Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/zachdunn/grok-plugin-claude-codeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/zachdunn/grok-plugin-claude-code/grok-cc)<a href="https://agentmods.dev/plugins/zachdunn/grok-plugin-claude-code/grok-cc"><img src="https://agentmods.dev/badge/plugins/zachdunn/grok-plugin-claude-code/grok-cc/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/zachdunn/grok-plugin-claude-code/grok-cc"><img src="https://agentmods.dev/badge/plugins/zachdunn/grok-plugin-claude-code/grok-cc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grok-cc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "grok-cc",
"version": "0.2.0",
"description": "Delegate and review code with the Grok CLI from Claude Code, like the codex plugin.",
"author": {
"name": "Zach Dunn",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 3 skills, 4 commands, 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 296 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 11 lines scan A fc06dea26a87
grok-cc is a plugin published in the GitHub repository zachdunn/grok-plugin-claude-code (32 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other plugins, from other repositories
grok
Consult xAI's Grok CLI from Claude Code for code review or arbitrary questions.
grok
Use Grok Build CLI from Claude Code to review code or delegate tasks.
grok-build
Claude Code ↔ Grok Build bridge for review, critique, and delegation.
codex
Use the local Codex CLI from Grok Build to review code or delegate tasks.
review
PR review, interactive git diff annotation review, and writing style guide.
github-ops
GitHub review, comment handling, and CI triage workflows with approval-gated write actions.