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/xzawed/claude-grok-build-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/xzawed/claude-grok-build-plugin/review)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/review"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-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.1 | $0.00013 | $0.00406 |
| Opus 5 | $0.00006 | $0.00203 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00041 |
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 8d 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
Post-delegation quality gate. Use after grok_build_delegate / verify / resume
(or when the user asks to review Grok's work).
Steps
- If you do not already have the last result, call
grok_build_usagewith projectcwdand noterecent[0]/lastSession/ insights. Do not inventsessionIds. - Inspect working tree diff for the files Grok touched (
filesChangedfrom the tool result, orgit status/git diffin the project). Prefer the listed paths; if worktree isolation was used, usegrok_build_worktreediff/apply as needed. - Check billing on the last Grok tool result:
- SuperGrok / X Premium+ sessions should show
billing: "subscription". - Unexpected
metered_api→ the server is running withGROK_BUILD_AUTH_MODE=api; that setting alone decides the tag (subscription mode strips the API-key vars before spawn).
- SuperGrok / X Premium+ sessions should show
- Adversarial review (Claude owns this — do not re-delegate the review itself):
- Correctness vs the original task
- Security / secrets / dangerous defaults
- Tests or docs left incomplete
- Scope creep outside the request
- Present a short verdict: accept / fix-with-Claude / fix-with-Grok (
/grok:resume) / discard (worktree remove if isolated). - Never commit or open a PR unless the user explicitly asks after the review.
Do not
- Auto-commit, auto-PR, or force-push
- Call Grok for HIGH-risk security/architecture final judgment without user intent
- Skip showing
filesChanged/ billing when available
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.
- 8d ago First seen · 33 lines · 13 tokens per session scan A e6fb55e4665a
review is a command published in the GitHub repository xzawed/claude-grok-build-plugin (1 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 406 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
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
spec
Spec-first design: a gap-closing interview that produces a complete spec, with a quality controller that blocks until every section is answered and every question resolved.
copilot-leak
Copilot's auto-review escapes: find them since the last look, sanitise them, and turn each one into a lesson.
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
docs
The documentation report: references, diagrams, drift, API docs, badges, README structure, links, Pages.