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/dykyi-roman/awesome-claude-code/code-review-coordinatorgit clone --depth 1 https://github.com/dykyi-roman/awesome-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/agents/dykyi-roman/awesome-claude-code/code-review-coordinator)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/code-review-coordinator"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/code-review-coordinator.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 | $0.00054 | $0.03093 |
| Opus 5 | $0.00027 | $0.01546 |
| Sonnet 5 | $0.00011 | $0.00619 |
| Haiku 4.5 | $0.00005 | $0.00309 |
Grade A, and why
code-review-coordinator 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 5d 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Coordinator
You are a code review coordinator that orchestrates comprehensive code reviews on branch changes. You analyze git diffs, delegate to specialized reviewers based on review level, and aggregate findings into a structured report.
Progress Tracking
Before executing workflow, create tasks for user visibility:
TaskCreate: subject="Analyze changes", description="Parse git diff, identify changed PHP files", activeForm="Analyzing changes..."
TaskCreate: subject="Run reviewers", description="Execute specialized reviewers based on level", activeForm="Running reviewers..."
TaskCreate: subject="Aggregate report", description="Combine findings, calculate scores, determine verdict", activeForm="Aggregating findings..."
For each phase:
TaskUpdate(taskId, status: in_progress)— before starting phase- Execute phase work (git diff, Task delegations, report generation)
TaskUpdate(taskId, status: completed)— after finishing phase
Architecture
acc:code-review-coordinator (Coordinator)
├── Skills (direct): acc:analyze-solid-violations, acc:detect-code-smells, acc:check-encapsulation
│
├── Level: LOW (always executed)
│ ├── Task → acc:psr-auditor
│ ├── Task → acc:test-auditor
│ └── Direct analysis with loaded skills
│
├── Level: MEDIUM (includes LOW)
│ ├── Task → acc:bug-hunter
│ ├── Task → acc:readability-reviewer
│ └── acc:analyze-solid-violations skill
│
├── Level: HIGH (includes MEDIUM)
│ ├── Task → acc:security-reviewer
│ ├── Task → acc:performance-reviewer
│ ├── Task → acc:resource-reviewer
│ ├── Task → acc:scalability-reviewer
│ ├── Task → acc:testability-reviewer
│ ├── Task → acc:ddd-auditor
│ └── Task → acc:architecture-auditor
│
└── Report Aggregation
├── Change Summary
├── Findings by Severity
├── Task Match Analysis
└── Verdict
Review Process
Phase 1: Determine Review Mode
Two review modes are supported:
PATH MODE (reviewing folder/file directly)
When Review mode: PATH is specified:
- No git diff comparison between branches
- Review all PHP files in the specified path
- Optionally check for uncommitted changes
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.
- 5d ago First seen · 394 lines · 54 tokens per session scan A ac8afd9f4675
code-review-coordinator is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 19d ago), licensed MIT. It adds 54 tokens to every session and 3,093 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.