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/tommymorgan/claude-plugins/code-reviewgit clone --depth 1 https://github.com/tommymorgan/claude-pluginsWhat 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.00023 | $0.01991 |
| Opus 5 | $0.00012 | $0.00996 |
| Sonnet 5 | $0.00005 | $0.00398 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade A, and why
tommymorgan:code-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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Orchestrator
Multi-agent code review with an optional fix loop that re-reviews after every fix cycle until the review comes back clean (not just until fixes are applied).
Step 1: Parse Arguments
Parse $ARGUMENTS for four things:
Review Aspects
Valid aspect keywords:
code— general code reviewtests— test quality analysiscomments— comment quality analysiserrors— silent failure detectiontypes— type design analysissimplify— code simplificationall— run all auto-detected agents (default when no aspect specified)
Fix Mode
fix— enable fix loop with default max of 5 iterationsfix:N(e.g.,fix:3) — fix loop with N max iterations- If absent: review-only mode
Execution Mode
parallel— run review agents simultaneously- If absent: sequential (default)
Auto Mode
auto— after the review agents produce findings, automatically dispatch the expert panel to debate every finding, then accept their consensus without prompting the user. Impliesfix(defaults tofix:5if no explicitfix:N).- If absent: interactive mode (present findings to user, fix loop requires user to invoke)
When auto is enabled:
- Review agents run and produce findings (Steps 2-5)
- Expert panel reviews ALL findings (not just in fix mode) — debates and reaches consensus
- Consensus is applied automatically: APPROVE → fix as suggested, MODIFY → fix with panel's revision, REJECT → skip
- Fixer agent applies all approved/modified fixes
- Full re-review cycle runs (Steps 2-5 again)
- Loop continues until clean or max iterations
The user sees progress updates but is never prompted for decisions. This is the "hands-off" mode for when you trust the review pipeline.
Step 2: Determine Diff
2a: Check for an open PR
gh pr view --json baseRefName -q .baseRefName 2>/dev/null
2b: Get the diff
- If a PR exists:
git diff $(git merge-base <base> HEAD)— includes committed and uncommitted changes - If no PR:
git diff $(git merge-base main HEAD)— all branch changes. If empty, fall back togit diff HEADfor uncommitted-only.
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.
- 2d ago First seen · 225 lines · 23 tokens per session scan A 24138dbe4ebb
tommymorgan:code-review is a command published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,991 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.