Borrowing it
Nothing to install: this file belongs to fletchgqc/agentbox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fletchgqc/agentbox/main/.claude/commands/recursive-review.mdgit clone --depth 1 https://github.com/fletchgqc/agentboxWrote 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/fletchgqc/agentbox/recursive-review)<a href="https://agentmods.dev/commands/fletchgqc/agentbox/recursive-review"><img src="https://agentmods.dev/badge/commands/fletchgqc/agentbox/recursive-review/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/commands/fletchgqc/agentbox/recursive-review"><img src="https://agentmods.dev/badge/commands/fletchgqc/agentbox/recursive-review.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00326 |
| Opus 5.5 | $0.00004 | $0.00130 |
| Sonnet 5.5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
recursive-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 2mo 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
You are a coordinator agent that orchestrates multiple specialized agents to conduct code review.
Steps:
Sequentially execute these three workflows:
-
Launch a Task agent with the prompt: 'Follow the instructions in .claude/commands/review.md with argument "$1" and save the results to the file review/review1.md. It should be just one review for all mentioned changes. Report only the file name back to the main agent.'
-
Launch a Task agent with the prompt: 'Conduct a critical evaluation of a code review. The review was performed on "$1" and is found in the file review/review1.md. Are the recommendations valid considering the project goals? Justify your reasoning. Save your results to review/evaluation1.md. It should be just one review for all mentioned changes. Report only the file name back to the main agent.'
-
Launch a Task agent with the prompt: 'Conclude the best way forward for the change request described by "$1". A review was made and stored at review/review1.md. An evaluation of this review was stored at review/evaluation1.md. Objectively consider the recommendations made by each party and decide the way forward, explaining your reasoning. Document your recommendation in conclusion1.md. Report only the file name back to the main agent.'
-
After all agents have completed, report summary of all processing
Important: Process files one at a time (serially) to avoid git branch conflicts. Do NOT launch agents in parallel.
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.
- 2mo ago First seen · 23 lines · 11 tokens per session scan A 49bc13ff2b4a
recursive-review is a command published in the GitHub repository fletchgqc/agentbox (120 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 326 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).