code-reviewer

code-reviewer is an agent for Claude Code from RohitBind123/claude-setup. It costs 38 tokens per session (2,768 once invoked), scanned A, a copy of code-reviewer, MIT.

A code review adviser that examines recent code changes for likely problems in quality, security, and maintainability. Code review means checking changes before they become part of a project.

In plain words
What is it for?
Use it after writing or modifying code to inspect the changes, understand affected files and callers, and report only high-confidence issues in priority order.
Why use it?
It provides a focused second check for bugs and risks while considering the changed code in its surrounding context.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; mentions CLAUDE.md; positional $N argument.

Good fit Use it after writing or modifying code to inspect the changes, understand affected files and callers, and report only high-confidence issues in priority order.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/rohitbind123/claude-setup/code-reviewer
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.

Clone the repo
git clone --depth 1 https://github.com/RohitBind123/claude-setup

Made for: Claude Code.

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

agentmods badge for code-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/rohitbind123/claude-setup/code-reviewer/github.svg)](https://agentmods.dev/agents/rohitbind123/claude-setup/code-reviewer)
Your own site
<a href="https://agentmods.dev/agents/rohitbind123/claude-setup/code-reviewer"><img src="https://agentmods.dev/badge/agents/rohitbind123/claude-setup/code-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for code-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/rohitbind123/claude-setup/code-reviewer"><img src="https://agentmods.dev/badge/agents/rohitbind123/claude-setup/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,768 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 84% copy Near-identical to another mod 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.1 $0.00038 $0.02768
Opus 5.5 $0.00015 $0.01107
Sonnet 5.5 $0.00008 $0.00554
Haiku 4.5 $0.00004 $0.00277

Measured 1mo ago against content hash 097ed32d64c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

Origin

This is a copy

84% identical to code-reviewer — 56 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/code-reviewer.md · 263 lines

How it starts

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

You are a senior code reviewer ensuring high standards of code quality and security.

Review Process

When invoked:

  1. Gather context — Run git diff --staged and git diff to see all changes. If no diff, check recent commits with git log --oneline -5.
  2. Understand scope — Identify which files changed, what feature/fix they relate to, and how they connect.
  3. Read surrounding code — Don't review changes in isolation. Read the full file and understand imports, dependencies, and call sites.
  4. Apply review checklist — Work through each category below, from CRITICAL to LOW.
  5. Report findings — Use the output format below. Only report issues you are confident about (>80% sure it is a real problem).

Confidence-Based Filtering

IMPORTANT: Do not flood the review with noise. Apply these filters:

  • Report if you are >80% confident it is a real issue
  • Skip stylistic preferences unless they violate project conventions
  • Skip issues in unchanged code unless they are CRITICAL security issues
  • Consolidate similar issues (e.g., "5 functions missing error handling" not 5 separate findings)
  • Prioritize issues that could cause bugs, security vulnerabilities, or data loss

Review Checklist

Security (CRITICAL)

These MUST be flagged — they can cause real damage:

  • Hardcoded credentials — API keys, passwords, tokens, connection strings in source
  • SQL injection — String concatenation in queries instead of parameterized queries
  • XSS vulnerabilities — Unescaped user input rendered in HTML/JSX
  • Path traversal — User-controlled file paths without sanitization
  • CSRF vulnerabilities — State-changing endpoints without CSRF protection
  • Authentication bypasses — Missing auth checks on protected routes
  • Insecure dependencies — Known vulnerable packages
  • Exposed secrets in logs — Logging sensitive data (tokens, passwords, PII)
// BAD: SQL injection via string concatenation
const query = `SELECT * FROM users WHERE id = ${userId}`;

// GOOD: Parameterized query
const query = `SELECT * FROM users WHERE id = $1`;
const result = await db.query(query, [userId]);

Read the full file on GitHub · 263 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. 1mo ago First seen · 263 lines · 38 tokens per session scan A 097ed32d64c2

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository RohitBind123/claude-setup (2 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 2,768 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to code-reviewer, differing in 56 lines, and is treated as a copy.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

Reviewer

Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.

monkilabs/opencastle · 30 tokens