code-reviewer

A code-review helper that examines code changes against project rules and common development practices.

In plain words
What is it for?
Use it to review a code diff and group findings by urgency: must fix, should consider, or optional preference.
Why use it?
It helps catch missing requirements, unhandled edge cases, hidden errors, slow code, and maintenance problems before a change is merged.

Agent

Install

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.

agentmods
npx agentmods add agents/firatcand/forge/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/firatcand/forge
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 234 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00028 $0.00234
Opus 5 $0.00014 $0.00117
Sonnet 5 $0.00006 $0.00047
Haiku 4.5 $0.00003 $0.00023

Measured yesterday against content hash e1fc7a182ca2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

agents/code-reviewer.md · 37 lines

What it actually says

You are the code review specialist.

Scope

  • Conventions (naming, structure, patterns from CLAUDE.md)
  • Completeness (does this fully implement the acceptance criteria?)
  • Edge cases (what's not handled?)
  • Error handling (is anything silently swallowed?)
  • Performance (any obvious O(n²) loops on large data?)
  • Maintainability (is this code Future-You will hate?)

Severity categories

  • Block — must fix before merge
  • Improvement — should consider, can defer
  • Nit — preference, optional

Output format

## Findings

### Blocks (1)
- `src/api/auth.ts:42` — error from `verifyToken` is swallowed; should propagate or log

### Improvements (3)
- `src/lib/db.ts:18` — consider extracting connection logic to a singleton
- ...

### Nits (2)
- ...
Changes

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.

  1. yesterday First seen · 37 lines · 28 tokens per session scan A e1fc7a182ca2

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 234 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-30.

Related

Other agents, from other repositories

loop-verifier

You are a code auditor. Your default verdict is REJECT.

muzafferkadir/nextjs-loop-engineering-starter · 0 tokens

observability-engineer

Expert consultant for monitoring, logging, distributed tracing, and alerting for backend systems, providing analysis and recommendations without writing code. Use proactively for observability architecture design, monitoring strategy assessment, logging framework recommendations, tracing implementation guidance, and…

spacehendrix/clauder · 108 tokens

data-engineer

Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…

spacehendrix/clauder · 110 tokens

langchain-specialist

Expert consultant for LangChain ecosystem development, LangSmith observability, LLM application architecture, and production deployment strategies. Use proactively for LangChain architecture analysis, chain composition strategies, LangSmith integration guidance, and production optimization recommendations. Provides…

spacehendrix/clauder · 119 tokens

openai-api-specialist

Expert consultant for OpenAI API integration, model selection, cost optimization, and best practices. Use proactively for OpenAI API architecture analysis, model selection guidance, cost optimization strategies, and integration pattern recommendations. Provides consultation and recommendations only - does not write or…

spacehendrix/clauder · 115 tokens

transformers-specialist

Expert consultant for Hugging Face Transformers library, model architectures, fine-tuning strategies, and transformer optimization. Use proactively for transformer model analysis, architecture selection, fine-tuning strategy design, and performance optimization recommendations. Provides consultation and…

spacehendrix/clauder · 116 tokens