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.
npx agentmods add commands/faeton/claude-grok-plugin/reviewgit clone --depth 1 https://github.com/faeton/claude-grok-pluginWrote 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/commands/faeton/claude-grok-plugin/review)<a href="https://agentmods.dev/commands/faeton/claude-grok-plugin/review"><img src="https://agentmods.dev/badge/commands/faeton/claude-grok-plugin/review.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00014 | $0.00517 |
| Opus 5 | $0.00007 | $0.00259 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
review 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 4d 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
Run a Grok code review through the local companion. Review only — Grok runs strictly read-only and web search is disabled; do not fix issues or apply patches in this turn.
Raw slash-command arguments:
$ARGUMENTS
Execution mode rules:
- If the raw arguments include
--wait, do not ask. Run in the foreground. - If the raw arguments include
--background, do not ask. Run with the companion's--background(it detaches its own worker — you do NOT need Claude'srun_in_background). - Otherwise, estimate the review size first:
- Working tree:
git status --short --untracked-files=all, plusgit diff --shortstat --cachedandgit diff --shortstat. - Base branch:
git diff --shortstat <base>...HEAD. - Treat untracked files as reviewable even when the diff stat is empty.
- Recommend waiting only when the change is clearly tiny (~1-2 files). Otherwise recommend background. When in doubt, run it.
- Working tree:
- Then use
AskUserQuestionexactly once with two options, recommended first with(Recommended):Wait for resultsRun in background
Argument handling:
- Preserve the user's arguments.
--scope,--base,--modelpass through to the companion. /grok:reviewdoes not take focus text. For focused/adversarial framing use/grok:adversarial-review.
Foreground:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" review $ARGUMENTS
Return the command stdout verbatim. Do not fix any issues mentioned.
Background:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" review --background $ARGUMENTS
Then tell the user: "Grok review started in the background. Check /grok:status for progress and /grok:result <id> for findings."
If the companion reports a failure, return it verbatim.
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.
- 4d ago First seen · 42 lines · 14 tokens per session scan A 0ba848ffd608
review is a command published in the GitHub repository faeton/claude-grok-plugin (1 stars, last pushed 20d ago), licensed MIT. It adds 14 tokens to every session and 517 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other commands, from other repositories
implement
Claude plans, Grok implements - write a concrete implementation plan, hand it to Grok as the worker, wait, then verify the result.
review
Run a Grok code review against local git state.
result
Show the stored final output for a finished Grok job in this repository.
transcript
Export the full Grok session transcript for a finished job (or any Grok session ID) as Markdown.
transfer
Transfer the current Claude Code session into a resumable Grok session.
setup
Check whether the local Grok Build CLI is ready and optionally toggle the stop-time review gate.