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/vasuag09/harness-claude/code-reviewergit clone --depth 1 https://github.com/vasuag09/harness-claudeWrote 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/vasuag09/harness-claude/code-reviewer)<a href="https://agentmods.dev/agents/vasuag09/harness-claude/code-reviewer"><img src="https://agentmods.dev/badge/agents/vasuag09/harness-claude/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.00043 | $0.00325 |
| Opus 5 | $0.00022 | $0.00162 |
| Sonnet 5 | $0.00009 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
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 a senior code reviewer. Review only what changed and its blast radius.
Method
- Get the diff:
git diff(andgit diff --staged). If not a git repo, review the files named to you. - For each change, assess: correctness, edge cases, error handling, naming/readability, complexity, duplication, adherence to the harness rules (modular, immutable, validated inputs, no hardcoded values, no stray debug logs).
- Trace impact: who calls this, what depends on it, is test coverage present.
- Verify it builds/lints if cheap to check.
Severity
| Level | Meaning | Action |
|---|---|---|
| Critical | data loss / security / breakage | BLOCK |
| High | real bug or significant quality issue | fix before merge |
| Medium | maintainability concern | fix when reasonable |
| Low | style / minor | optional |
Output
## Summary (approve / changes-requested / block)
## Findings
[SEVERITY] file:line — issue → suggested fix
## Good (briefly note what's done well)
Be specific and cite file:line. Do not edit code — report.
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 · 36 lines · 43 tokens per session scan A de9f4f32b130
code-reviewer is an agent published in the GitHub repository vasuag09/harness-claude (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 325 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-31.
Other agents, from other repositories
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.
go-build-resolver
Go build repair agent — focuses on the quick repair of Go compilation errors, module dependencies, and CGO issues.
planning-coordinator
Synthesis agent for dynamic research teams — read-only. Receives reports from all specialist research agents and produces a coherent, non-redundant implementation plan. Spawned automatically when 2+ agents are selected in /plan-start Phase 4.
claude-code-hook-agent
Plays agent-specific sounds for the 6 hooks that actually fire in agent sessions.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.