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/MadAppGang/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/commands/madappgang/claude-code/review)<a href="https://agentmods.dev/commands/madappgang/claude-code/review"><img src="https://agentmods.dev/badge/commands/madappgang/claude-code/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/madappgang/claude-code/review"><img src="https://agentmods.dev/badge/commands/madappgang/claude-code/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.00015 | $0.17052 |
| Opus 5.5 | $0.00006 | $0.06821 |
| Sonnet 5.5 | $0.00003 | $0.03410 |
| Haiku 4.5 | $0.00002 | $0.01705 |
Grade D, and why
frontend-review scanned grade D with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SETTINGS=$(cat .claude/settings.json 2>/dev/null) Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$dir" 2>/dev/null && echo "Cleaned: $(basename $dir) (age)" How it starts
The opening of the file, as written. The whole thing — 1,784 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provide developers with high-confidence feedback by aggregating reviews from multiple
AI models, highlighting issues flagged by majority consensus while maintaining cost
transparency and enabling graceful fallback to embedded Claude reviewer.
<user_request> $ARGUMENTS </user_request>
<critical_override> THIS COMMAND OVERRIDES THE CLAUDE.md TASK ROUTING TABLE FOR AGENT SELECTION.
WHY: ALL code reviews in this command MUST use frontend:senior-code-reviewer agent (subagent_type: "frontend:reviewer") because it is the ONLY frontend agent that handles external models via Bash+claudish CLI. The CLAUDE.md routing table might substitute dev:architect or agentdev:reviewer, which lack frontend-specific review patterns.
AGENT RULES FOR THIS COMMAND:
- ALL code reviews (embedded and external) → frontend:reviewer agent (subagent_type: "frontend:reviewer")
- Consolidation → Orchestrator (reads files, analyzes consensus, NOT delegated)
DO NOT use dev:architect, agentdev:reviewer, or any other reviewer agent. ONLY frontend:reviewer (senior-code-reviewer) correctly handles external model routing for this plugin. </critical_override>
**✅ You MUST:**
- Use Task tool to delegate ALL reviews to senior-code-reviewer agent
- Use Bash to run git commands (status, diff, log)
- Use Read/Glob/Grep to understand context
- Use Tasks to track workflow progress (all 5 phases)
- Use AskUserQuestion for user approval gates
- Execute external reviews in PARALLEL (single message, multiple Task calls)
**❌ You MUST NOT:**
- Write or edit ANY code files directly
- Perform reviews yourself
- Write review files yourself (delegate to senior-code-reviewer)
- Run reviews sequentially (always parallel for external models)
</orchestrator_role>
<cost_transparency>
Before running external models, MUST show estimated costs and get user approval.
Display cost breakdown per model with INPUT/OUTPUT token separation and total
estimated cost range (min-max based on review complexity).
</cost_transparency>
<graceful_degradation>
If Claudish unavailable or no external models selected, proceed with embedded
Claude Sonnet reviewer only. Command must always provide value.
</graceful_degradation>
<parallel_execution_requirement>
CRITICAL: Execute ALL external model reviews in parallel using multiple Task
invocations in a SINGLE message. This achieves 3-5x speedup vs sequential.
Example pattern:
[One message with:]
Bash: claudish --model model-1 ...
---
Bash: claudish --model model-2 ...
---
Bash: claudish --model model-3 ...
This is the KEY INNOVATION that makes multi-model review practical (5-10 min
vs 15-30 min). See Key Design Innovation section in knowledge base.
</parallel_execution_requirement>
<todowrite_requirement>
You MUST use the Tasks system to create and maintain a todo list throughout
your orchestration workflow.
**Before starting**, create a task list with all workflow phases:
1. PHASE 1: Ask user what to review
2. PHASE 1: Gather review target
3. PHASE 2: Present model selection options
4. PHASE 2: Show estimated costs and get approval
5. PHASE 3: Execute embedded review
6. PHASE 3: Execute ALL external reviews in parallel
7. PHASE 4: Read all review files
8. PHASE 4: Analyze consensus and consolidate feedback
9. PHASE 4: Write consolidated report
10. PHASE 5: Present final results to user
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 · 1,784 lines · 15 tokens per session scan D 414b42afa42c
frontend-review is a command published in the GitHub repository MadAppGang/claude-code (285 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 17,052 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.