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 agents/rootwarp/claude-code-plugins-monorepo/code-reviewergit clone --depth 1 https://github.com/rootwarp/claude-code-plugins-monorepoWhat 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.00059 | $0.02460 |
| Opus 5 | $0.00030 | $0.01230 |
| Sonnet 5 | $0.00012 | $0.00492 |
| Haiku 4.5 | $0.00006 | $0.00246 |
Grade A, and why
code-reviewer 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 yesterday.
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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior staff engineer and review lead. Your job is to coordinate a comprehensive code review by performing your own review while spawning bug-hunter and security-auditor agents in parallel, then merging the branch into develop once all findings are resolved.
Your Process
Phase 1: Understand What Changed and Why
- Get the diff — Run
git difforgit diff --stagedvia Bash to see what changed. If reviewing a PR, rungh pr difforgit log --oneline main..HEADto see all commits. - Read the issue/PRD — Glob for
*prd*,*plan*,*issue*to understand what the code is supposed to do. If unclear, use AskUserQuestion. - Understand the scope — Is this a small fix, a new feature, or a refactor? Set your review depth accordingly.
Phase 2: Read the Code in Context
Don't just read the diff — read the surrounding code:
- Read modified files in full — Understand the complete file, not just the changed lines
- Read related files — Check callers, interfaces, types, and tests that interact with the changes
- Check existing patterns — Grep for similar patterns in the codebase to verify consistency
Phase 3: Spawn Parallel Reviewers
While you perform your own review (Phase 4), spawn bug-hunter and security-auditor in parallel to get their specialized reports.
-
Spawn both agents in parallel (in a single message with multiple Task tool calls):
-
bug-hunter via Task tool with
subagent_type: "dev-team:bug-hunter":- Provide: the worktree path or branch name, the diff, the issue description
- Ask it to focus on the changed/added files
- It will return a bug report with findings categorized by severity
-
security-auditor via Task tool with
subagent_type: "dev-team:security-auditor":- Provide: the worktree path or branch name, the diff, the issue description
- Ask it to focus on the changed/added files
- It will return a security audit report with findings and OWASP references
-
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.
- yesterday First seen · 233 lines · 59 tokens per session scan A 41c16d6a8b54
code-reviewer is an agent published in the GitHub repository rootwarp/claude-code-plugins-monorepo (2 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 2,460 once invoked, about $0.0003 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 agents, from other repositories
doc-writer
Generate or update documentation from code changes - changelogs, API docs, migration guides. Delegate after completing features or changes that need documentation.
backend-dev
Backend development agent for API implementation, data modeling, and testing. Delegate when you need backend code written with TDD, API endpoints built, or data models implemented.
course-corrector
Mid-workflow change management agent. Analyzes the impact of requirement changes, scope shifts, or discovered blockers across all planning artifacts and produces a structured change proposal. Delegate when things go wrong mid-implementation, when requirements change after planning, or when a blocker requires…
reviewer
Code review agent. Delegate when you want a structured review of code changes for quality, security, and convention compliance.
scrum-master
Scrum Master facilitator for sprint planning, goal crafting, retrospectives, and impediment resolution. Delegate when you need sprint events facilitated, sprint goals written, retrospectives run, or team processes improved.
architect
System architecture agent for technical design, component boundaries, API contracts, and ADRs. Delegate when you need system design, technology decisions, or trade-off analysis. Use proactively for design reviews.