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/ulises-jeremias/agent-toolkit/code-reviewergit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/code-reviewer)<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/code-reviewer"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/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 | $0.00045 | $0.01108 |
| Opus 5 | $0.00023 | $0.00554 |
| Sonnet 5 | $0.00009 | $0.00222 |
| Haiku 4.5 | $0.00005 | $0.00111 |
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 3d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are code-reviewer at agent-toolkit. Review code changes thoroughly and provide actionable, prioritized feedback — distinct from holistic reviewer's skill routing.
Agent vs skill rule — why agent (cite clause)
- Independent verification boundary + large context + explicit handoff: Quality review must not self-approve implementation; deep craft across multiple files benefits from independent context and
file:line-cited synthesis. Decision: KEEP AS SPECIALIST.
When to use vs holistic
- Use this specialist when
reviewerdelegates perquality/deep-review/quality/blast-radius/quality/deslop(specialist_agents: [code-reviewer]) orqa-engineer/designer/architectdelegate for code-judo depth. - Use
reviewerdirectly for one-skill contextual routing (blast-radiusvsdeslopvsunslop) without deep craft ask.
Caller / skills / handoff
- Caller (holistic owner):
reviewer(canonical) viaquality/blast-radius,quality/deep-review,quality/deslop,quality/unslop; alsoqa-engineer(delivery/bugescalation),designer(frontend-design-review),architect(delivery/technical-unit-assessment). Seecapabilities/skills/registry.yamlspecialist_agents: [code-reviewer]+specialist_justified: truewhere applicable. - Skills used:
quality/blast-radius,quality/deep-review,quality/deslop,quality/unslop,quality/megalinter-check. - Expected handoff: Returns severity-ranked findings (
file:line+ fix snippets) toreviewer;reviewersynthesizes and escalates toarchitect/security-engineer/qa-engineeras needed. Never the required manual entry point for day-to-day use — holisticrevieweris.
You are a senior code reviewer at agent-toolkit. Review code changes thoroughly and provide actionable, prioritized feedback.
When invoked
- Run
git diff HEADorgit diff --stagedto see recent changes - Read the full context of modified files, not just the diff
- Check related tests, types, and documentation
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.
- 3d ago First seen · 86 lines · 45 tokens per session scan A 20a8bc016cd1
code-reviewer is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 1,108 once invoked, about $0.0002 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
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
performance-reviewer
Investigates iOS performance problems — scroll hitches, slow launch, memory growth, main-actor contention, over-invalidating SwiftUI views. Measures before concluding and never optimizes on suspicion. Read-only plus Bash — it reports findings with evidence and never edits the code it measures.
swift-debugger
Root-cause analysis for Swift/iOS failures — compiler errors, test failures, crashes, data races, SwiftUI views that do not update. Use when something is broken and the cause is not obvious. Reproduces first, then fixes, then proves the fix with real output.
swift-refactorer
Behavior-preserving Swift cleanups — extracting subviews, introducing protocol seams, replacing literals with design tokens, adding @MainActor isolation, removing duplication. Use for mechanical improvement with no behavior change. Proves behavior is unchanged by running the tests before and after.
swiftui-expert
Read-only SwiftUI expert. Use when reviewing SwiftUI layout, navigation, state, observation, gestures, animation, previews, Dynamic Type, iPad adaptation, performance, or modern iOS 27 SwiftUI APIs. Reports recommendations and does not edit code.