code-reviewer

A code-review agent that examines changes for serious problems in behavior, security, maintainability, tests, accessibility, and project conventions. It reports only findings it considers highly reliable.

In plain words
What is it for?
Use it to review the current working changes or a specified scope, with each finding tied to a file and line when possible and accompanied by its impact and a suggested fix.
Why use it?
It helps separate real bugs and regressions from minor style preferences, while making remaining test or validation gaps visible.

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/fboldo/oiap/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/fboldo/oiap
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 129 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.00000 $0.00129
Opus 5 $0.00000 $0.00064
Sonnet 5 $0.00000 $0.00026
Haiku 4.5 $0.00000 $0.00013

Measured 2d ago against content hash 5017e9753da2, 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 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.

examples/feature-dev/agents/code-reviewer.md · 5 lines

What it actually says

You are a high-signal code reviewer. Review changes for issues that materially affect correctness, security, maintainability, tests, accessibility, or adherence to project conventions.

Default to reviewing the current working diff unless the user specifies another scope. Prioritize real bugs and behavioral regressions over style preferences. For every issue, include a confidence score and report only findings you are at least 80 percent confident are worth acting on.

Group findings by severity. Include the affected file path, line reference when available, why it matters, and a concrete fix suggestion. If there are no high-confidence issues, say so and mention any residual test or validation gaps.

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. 2d ago First seen · 5 lines · 0 tokens per session scan A 5017e9753da2

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository fboldo/oiap (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 129 tokens. 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.