Cc Thingz plugin for Grok Build
Portable skills, agents, hooks, and Pi extensions for Claude Code, Codex CLI, Copilot, Cursor, Grok, and Pi.
How to install Cc Thingz in Grok Build
1. Add this repo as a plugin marketplace in Grok Build (once per computer):
grok plugin marketplace add alexei-led/cc-thingz2. Install the plugin:
grok plugin install browser@alexei-led/cc-thingz --trustReview before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.
This repo's marketplace has 7 plugins; we checked browser, dev-flow, discovery. Install another the same way: grok plugin install <name>@alexei-led/cc-thingz --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.
Inside Grok Build: type /plugins, open the Marketplace tab, press a and add alexei-led/cc-thingz, then select browser and press i.
Command format: Grok Build's plugin guide
What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 15 skills, 3 subagents. That's an install check only: we haven't run it in a live Grok session.
New Grok Build plugins every Tuesday, install line ready to copy.
Stacks Weekly is one short email from GrokStacks and CodexStacks. Subscribe and get the free starter list: 20 Grok Build plugins worth installing first.
Confirmation email first. Unsubscribe anytime.
What it contains
Skills (15)
browser-automation— Browser automation for rendered UI exploration, validation, screenshots, recordings, and end-to-end flows. Use when a task needs an actual browser or rendered DOM: inspect UI state, click/fill forms, debug frontend behavior, capture evidenccommitting-code— Create normal git commits with logical grouping. Use when committing, saving changes, creating commits, or grouping work into commits. For drafting or editing commit messages without committing, use writing-style. NOT for amending, rebasingdocumenting-code— Write, rewrite, or update project docs from implementation facts - README front pages, user guides, configuration references, architecture docs, evaluations, agent instructions, and code comments. Use when writing or improving project docsfixing-code— Fix code defects with a reproducible feedback loop, root-cause diagnosis, minimal patch, regression test, and clean verification. Use when debugging, diagnosing, or resolving lint/test/build failures. NOT for test-suite cleanup without a primproving-tests— Improve test design, speed, and coverage with behavior-focused tests, useful seams, characterization tests, TDD, and test refactoring. Use when improving tests, optimizing slow suites, adding coverage, refactoring brittle tests, removing tereleasing-code— Prepare, publish, or repair a software release and write its release notes. Use for cutting a versioned release or editing release notes. NOT for updating an installed package, publishing articles, or discussing a release; for general documreviewing-code— Use when reviewing changed code, PRs, diffs, or specific files. Finds evidence-backed defects in security, correctness, tests, reliability, performance, maintainability, and docs. Supports quick, standard, deep, team, and external-review mowriting-style— Write or edit commit messages, PR/MR descriptions, issues, review comments, and technical discussions. Use for concise, clear engineering communication grounded in facts, without filler or boilerplate. NOT for creating commits (committing-cbrainstorming-ideas— Brainstorm ideas and stress-test draft plans before coding. Use when brainstorming, exploring approaches, designing a feature/API/flow, grilling or debating a bounded plan, challenging assumptions, or resolving design-blocking terminology.evolving-config— Audit and improve AI coding-agent configuration. Use when reviewing or changing Claude Code, Pi, Codex, Copilot, Cursor, Grok, skill, agent, hook, MCP, permission, package, or generated-export setup. Default is review-only; fixes require exinstallation-doctor— Diagnose cc-thingz plugin installations with the bundled read-only doctor. Use for missing installed skills, helpers, or hook files, stale package versions, duplicate packages, or migration from old cc-thingz packages. NOT for broad agent clooking-up-docs— Find exact, version-correct library/API/framework docs through one lookup workflow. Use when the user says "look up docs", "how to use", "API for", "syntax for", "examples of", "show me the docs", mentions "ctx7"/"Context7", passes a `/org/researching-web— Web research via platform web tools. Use for technical comparisons, current-state and release-behavior questions, recent facts, ecosystem news, best practices, standards, or questions needing grounded web evidence. NOT for exact API syntax,reviewing-instructions— Use when asked to lint, audit, review, or score AI-facing instruction files such as SKILL.md, AGENT.md, AGENTS.md, CLAUDE.md, platform body.md files, prompt files, rules, policies, and agent-facing references. NOT for plugin manifests, applwriting-skills— Create, split, slim, or rewrite repository skills. Use when adding a new `src/skills/<name>/` skill, editing a skill description, frontmatter, references, overlays, or plugin placement, or tightening routing between neighboring skills. NOT
Subagents (6)
browser:engineer— Sole mutator role — applies and verifies code, test, doc, and infra changes. Has Edit/Write/Bash and runs the project build/test/lint gate on what it changed. Use for implement, fix, refactor, or appldev-flow:engineer— Sole mutator role — applies and verifies code, test, doc, and infra changes. Has Edit/Write/Bash and runs the project build/test/lint gate on what it changed. Use for implement, fix, refactor, or appldev-flow:reviewer— Read-only adversarial evaluator — reviews, audits, locates, or plans. Reads files, searches, and inspects diffs with available read-only tools; never modifies code or runs builds/tests. Use for code rdiscovery:engineer— Sole mutator role — applies and verifies code, test, doc, and infra changes. Has Edit/Write/Bash and runs the project build/test/lint gate on what it changed. Use for implement, fix, refactor, or appldiscovery:reviewer— Read-only adversarial evaluator — reviews, audits, locates, or plans. Reads files, searches, and inspects diffs with available read-only tools; never modifies code or runs builds/tests. Use for code rdiscovery:runner— Fast utility lane for simple bounded tasks on a cheaper model when available. Use proactively for file lookup, grep/glob searches, `git status/log/show/diff`, file reads, log summaries, and focused sh
Hooks (1)
hooks— Notification, PostToolUse, PreToolUse, SessionStart, Stop, UserPromptSubmit
Plugins in this marketplace (7)
browser— Browser-based testing, validation, screenshots, recordings, and quick automationdev-flow— Code review, fixes, commits, release flows, and linting for development workflowsdiscovery— Research, docs lookup, utility routing, skill authoring, instruction review, and agent configuration auditsgit-flow— Git worktrees, branch cleanup, hooks, secret scanning, config hygiene, and guardrailsinfra-ops— Kubernetes, Terraform, Helm, GitHub Actions, AWS, GCP, and Linux infrastructure operationsprogramming— Idiomatic development across C# /.NET, Go, Java/Kotlin, Python, Rust, TypeScript, shell, and webspec-flow— Lightweight spec loop: plan one slice, execute one task, checkpoint or close
About this listing
Cc Thingz is a community plugin on GitHub by alexei-led, built for Grok Build. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 15 skills, 6 subagents, 1 hook, 7 plugins in this marketplaces. Its license is MIT. We checked commit 0a6445bf79e8. It's one of 410 listings in the Development category on GrokStacks.
Cc Thingz FAQ
How do I install Cc Thingz in Grok Build?
Add the repo as a marketplace with grok plugin marketplace add alexei-led/cc-thingz, then run grok plugin install browser@alexei-led/cc-thingz --trust. This repo's marketplace has 7 plugins; we checked browser, dev-flow, discovery. Install another the same way: grok plugin install <name>@alexei-led/cc-thingz --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.
Is Cc Thingz an official Grok Build plugin?
No. Cc Thingz is a community plugin on GitHub by alexei-led, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.
What does Cc Thingz include?
According to what Grok loaded in our install check, Cc Thingz includes 15 skills, 6 subagents, 1 hook, 7 plugins in this marketplaces: browser-automation, committing-code, documenting-code, fixing-code, improving-tests, releasing-code….
Details
- Type
- Plugin
- Category
- Development
- Source
- Community plugin, built for Grok Build
- License
- MIT
- Author
- alexei-led
- Keywords
- agent-skills, agentbundler, ai-coding, claude-code, claude-code-marketplace, claude-code-plugin, code-review, codex, codex-cli, codex-cli-plugin, coding-agents, cursor
- Source repo
- https://github.com/alexei-led/cc-thingz
- Checked commit
0a6445bf79e8- Checked by GrokStacks
- Install-checked in Grok Build on Oct 18, 2026; not run in a live session
Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.
For maintainers: badge and embeds
Maintain Cc Thingz? Add the badge; it links to this page.
Markdown
[](https://grokstacks.com/p/cc-thingz/)HTML
<a href="https://grokstacks.com/p/cc-thingz/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>Embed card (static HTML and inline CSS, no JavaScript). Preview:
<a href="https://grokstacks.com/p/cc-thingz/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">Cc Thingz</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 15 skills, 6 subagents, 1 hook, 7 plugins in this marketplaces</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">Portable skills, agents, hooks, and Pi extensions for Claude Code, Codex CLI, Copilot, Cursor, Grok, and Pi.</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>Markdown summary
**[Cc Thingz on GrokStacks](https://grokstacks.com/p/cc-thingz/)**: Community plugin for Grok Build with 15 skills, 6 subagents, 1 hook, 7 plugins in this marketplaces. Install: `grok plugin install browser@alexei-led/cc-thingz --trust` (after `grok plugin marketplace add alexei-led/cc-thingz`)More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.
Also in Development
abap2UI5
Build UI5 Apps Purely in ABAP
Accessibility Agents
Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating inaccessible code.
addyosmani/agent-skills
Production-grade engineering skills for AI coding agents.
Advise Project Approach
A portable project-planning skill for Codex, Claude Code, pi, Hermes, and Agent Skills-compatible harnesses. Evidence before build advice.
Agent Bridge
A local bridge for bidirectional collaboration between Claude Code and Codex. 连接 Claude Code 与 Codex 的本地实时协作桥接工具。
Agent Harness
Our agent harness: Skills, plugins, hooks, and utilities to improve the quality of your agent.