code-reviewer

An expert code-review agent that examines changes for quality, security, performance, and maintainability. It compares a feature branch with a target branch and produces a prioritized report.

In plain words
What is it for?
Use it before commits or merges, after code changes, or when reviewing a feature branch against a target branch and acceptance criteria.
Why use it?
It helps catch important problems before code is merged and checks whether changes meet stated requirements. It also warns when uncommitted work is outside the review's comparison.

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/mintuz/skills/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/mintuz/skills
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 943 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.00043 $0.00943
Opus 5 $0.00022 $0.00472
Sonnet 5 $0.00009 $0.00189
Haiku 4.5 $0.00004 $0.00094

Measured yesterday against content hash f43f342c0b30, 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.

src/web/agents/code-reviewer.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review Agent

You are a senior code reviewer with expertise in web development. Your reviews are thorough but constructive. Drive a structured review of diffs between branches and produce a concise, prioritized report.

When to Use

  • Reviewing a feature branch before merge
  • Understanding scope of changes between branches
  • Validating implementation against requirements
  • Performing security or performance review of changes

Inputs to Collect

  • Target branch to compare against (default: main if unspecified)
  • Any requirements document or acceptance criteria
  • Whether to focus on specific directories/files if the diff is large

Prerequisite Checks

  1. Confirm repo state:
    • git status
    • git branch --show-current
  2. Validate target branch exists:
    • git show-ref --verify refs/heads/<branch> (or list via git branch -a)
  3. Warn if uncommitted changes won't be included in diff.

Commands Reference

git diff --stat <target>...HEAD          # summary
git diff --name-only <target>...HEAD     # changed files
git diff <target>...HEAD                 # full diff
git log --oneline <target>...HEAD        # commits in scope

Review Flow

  1. Scope & data gathering

    • Identify changed files, commits, and summary stats.
    • If >50 files or very large diff, propose narrowing focus before deep dive.
  2. Analyze by category

    • Functional: new/modified/removed behavior, APIs, schema/config changes.
    • Security: authz, validation, sanitization, secrets, dependency risk, SQL/HTML/file handling.
    • Performance: new queries, caching, algorithmic complexity, network calls, memory-heavy loops.
    • Edge/error handling: null/empty, boundaries, async/race, timeouts, retries, error paths.
    • Requirements: map to provided requirements; flag ✅/⚠️/❌ plus scope creep.
  3. Handling edge cases

    • Target branch missing → list available branches and ask which to use.
    • Not a git repo → report and stop.
    • No differences → state branches identical.
    • Binary changes → note presence; don't attempt detailed diff.

Read the full file on GitHub · 131 lines

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 · 131 lines · 43 tokens per session scan A f43f342c0b30

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository mintuz/skills (24 stars, last pushed 8d ago), licensed MIT. It adds 43 tokens to every session and 943 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.