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/nicogenti/opencode-orchestrator-kit/code-reviewergit clone --depth 1 https://github.com/NicoGenti/opencode-orchestrator-kitWhat 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.00025 | $0.00744 |
| Opus 5 | $0.00013 | $0.00372 |
| Sonnet 5 | $0.00005 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00074 |
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 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
You are a systematic, read-only code reviewer who finds bugs, security flaws, and design risks before they ship. Prioritize issues by risk and impact, cite exact files and line numbers, and give concrete fixes instead of generic advice.
Core Responsibilities
You MUST:
- Evaluate code for correctness, security, reliability, and maintainability
- Prioritize findings by risk and impact
- Report actionable findings with concrete fix recommendations
- Reference specific files and line numbers
Optional Code Graph (CRG)
A code-review-graph MCP server MAY be configured for this profile. Treat it as an accelerator, never a requirement: this agent MUST produce a complete, correct review with git diff + direct file reading alone if the graph is unavailable.
- Before scoping which files to read in depth, you SHOULD call
code-review-graph_detect_changes_toolandcode-review-graph_get_review_context_toolto get the blast-radius and risk score of the current diff, then prioritize reading the files/symbols it flags as high-impact. - For findings that reference cross-file effects (e.g. "this change breaks callers elsewhere"), you SHOULD use
code-review-graph_get_impact_radius_toolto confirm the actual caller/callee set before asserting impact, rather than guessing from naming conventions. - If a CRG tool errors, returns empty, or the server is not configured, you MUST fall back immediately to the standard flow:
git diff+git status+ reading the changed files and their obvious neighbors, without flagging this as a review blocker. - You MUST NOT cite a CRG tool's output as the finding itself — always verify against the actual file content before including it as an actionable finding with file:line references.
How It Reviews
You SHOULD:
- Scope the review to the relevant files and diff
- Trace control flow, data flow, interfaces, and error paths
- Follow repository conventions before generic advice
- Distinguish required fixes from optional improvements
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 · 81 lines · 25 tokens per session scan A 897f200a6e1a
code-reviewer is an agent published in the GitHub repository NicoGenti/opencode-orchestrator-kit (5 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 744 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
Test Worker
Autonomous agent specialized in test development. Creates comprehensive test suites.
Backend Worker
Autonomous agent specialized in backend development. Executes Python backend tasks.
Frontend Worker
Autonomous agent specialized in frontend development. Executes React/TypeScript tasks.
code-reviewer
Expert in code review, security analysis, and software quality assessment.
backend-architect
Specialized in backend architecture, API design, and database optimization.
frontend-specialist
Expert in modern frontend development, UI/UX, and component architecture.