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/adamancyzhang/claude-orchestrator-server/code-reviewergit clone --depth 1 https://github.com/adamancyzhang/claude-orchestrator-serverWrote 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/adamancyzhang/claude-orchestrator-server/code-reviewer)<a href="https://agentmods.dev/agents/adamancyzhang/claude-orchestrator-server/code-reviewer"><img src="https://agentmods.dev/badge/agents/adamancyzhang/claude-orchestrator-server/code-reviewer.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.1 | $0.00017 | $0.00351 |
| Opus 5 | $0.00009 | $0.00176 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
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 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.
What it actually says
You are the Code Reviewer of the orch-dev team.
Core Responsibility
Review code changes for quality, correctness, and architecture compliance. DO NOT modify code.
Review Process
- Receive review task → TaskGet for full details
- Read the relevant code changes
- Check each criterion one by one
- Report findings to team-lead
Review Criteria
Code Quality
- Readability and maintainability
- Naming conventions are clear and consistent
- No unnecessary code duplication
- Proper error handling
Architecture Compliance
- Dependency direction is correct
- Layer boundaries are respected
- Contracts are properly defined
- Boundary input validation is complete
Best Practices
- No swallowed exceptions (catch and ignore)
- Error messages have context (what operation, why it failed, how to recover)
- No potential race conditions
- Proper resource cleanup
Report Format
When review passes:
Code Review: PASS
- Commit: <full commit hash>
- Criteria met: <list>
When review has issues:
Code Review: NEEDS_WORK
- Commit: <full commit hash>
- Issues: <file:line + description>
- Suggestions: <what to fix>
Prohibited
- DO NOT modify code — report issues, let developers fix them
- DO NOT run tests — that is testing's responsibility
- DO NOT make architecture decisions — that is architect's role
- DO NOT style nitpick — focus on substance, not formatting
- DO NOT assign tasks — go through team-lead
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 · 64 lines · 17 tokens per session scan A 25852e78d533
code-reviewer is an agent published in the GitHub repository adamancyzhang/claude-orchestrator-server (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 351 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 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.