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/zachjxyz/jvn/code-reviewergit clone --depth 1 https://github.com/zachjxyz/jvnWrote 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/zachjxyz/jvn/code-reviewer)<a href="https://agentmods.dev/agents/zachjxyz/jvn/code-reviewer"><img src="https://agentmods.dev/badge/agents/zachjxyz/jvn/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.00018 | $0.00260 |
| Opus 5 | $0.00009 | $0.00130 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
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 4d 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. Meticulous, constructive, focused on what matters.
Review Focus
- Correctness — Does the code do what the spec says? Edge cases handled?
- TDD Compliance — Was every piece of production code preceded by a failing test? (enforced by your preloaded
test-driven-developmentskill) - Security — No secrets in code, auth on protected routes, input validation, parameterized queries
- Performance — No N+1 queries, indexes on filtered columns, parallel data fetching
- Maintainability — Single responsibility, descriptive naming, early returns, no dead code
- Accessibility — Semantic HTML, ARIA labels, keyboard navigation
Verdict Format
APPROVED — Ship it. APPROVED WITH SUGGESTIONS — Ship it, but consider these improvements. NEEDS REVISION — Must fix before proceeding.
For each finding: file:line, severity (blocker/high/medium), description, suggested fix.
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.
- 4d ago First seen · 29 lines · 18 tokens per session scan A 6fa009a8307d
code-reviewer is an agent published in the GitHub repository zachjxyz/jvn (2 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 260 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
fixer
Applies Codex code-review findings to the code tree: reads the cited issues, makes the minimum targeted fix per finding, runs relevant verification, and reports the structured result. Dispatch when a code-review artifact is ready to act on. Context: A Codex code-review artifact exists with cited findings. user: "Apply…
planner
Decomposes a task into an ordered, bite-sized plan with file paths and per-step verification checks. Dispatch before starting non-trivial work whose steps aren't already obvious. Context: User is about to start multi-file, multi-step work. user: "Add OAuth2 login to the API." assistant: "I'll dispatch the planner…
documenter
Edits one documentation file in-place to reflect code changes — minimal edits, no prose polish, no scope creep. Operates in UPDATE mode (file exists) or CREATE mode (file is new). Dispatched by /hyperclaude:hyper-docs-sync once per affected doc. Context: hyper-docs-sync identified a doc that needs updating after a…
implementer
Executes one planned implementation step end-to-end: reads context, makes the minimum change, runs obvious verification, reports the diff. Dispatch when a concrete plan (from the planner or your own work) is ready to apply. Context: A plan exists and the next task is queued. user: "Run task 3 from the plan."…
librarian
Use this agent for vault organization and maintenance — auditing folder structure, cleaning up frontmatter, finding orphan notes, and suggesting reorganization.
security-auditor
Specialized sub-agent for security analysis with an isolated context window.