code-reviewer

code-reviewer is an agent for Claude Code, Kiro from affaan-m/ECC. It costs 38 tokens per session (2,038 once invoked), scanned A, original, MIT.

A general code reviewer that examines recent changes for bugs, security problems, maintainability issues, and regressions—unintended breakage caused by a change.

In plain words
What is it for?
Use it after writing or modifying code to inspect the diff, understand surrounding code, and report high-confidence issues before committing.
Why use it?
It focuses attention on likely real problems in the changed code and avoids filling the review with minor style preferences or unsupported concerns.

Agent for Claude CodeKiro

Written for Claude Code and Kiro: shipped in a Claude Code plugin, but also installed under .kiro/. Also seen: mentions CLAUDE.md; positional $N argument.

Part of the ecc plugin — 78 skills, 58 commands, 70 agents, 1 MCP server shipped together

Good fit Use it after writing or modifying code to inspect the diff, understand surrounding code, and report high-confidence issues before committing.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/affaan-m/ecc/code-reviewer
About the project

ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.

affaan-m/ECC · 280,368 stars · on GitHub · ecc.tools

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/affaan-m/ECC

Made for: Claude Code, Kiro.

Or install ecc, the plugin that ships this one along with the rest of its 78 skills, 58 commands, 70 agents, 1 MCP server.

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/affaan-m/ecc/code-reviewer/github.svg)](https://agentmods.dev/agents/affaan-m/ecc/code-reviewer)
Your own site
<a href="https://agentmods.dev/agents/affaan-m/ecc/code-reviewer"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/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/affaan-m/ecc/code-reviewer"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/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,038 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. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review
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.1 $0.00038 $0.02038
Opus 5.5 $0.00015 $0.00815
Sonnet 5.5 $0.00008 $0.00408
Haiku 4.5 $0.00004 $0.00204

Measured 1mo ago against content hash d454138768cd, 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

Copies of this mod

8 near-identical copies found in the catalogue:

.kiro/agents/code-reviewer.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 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 · 239 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 · 239 lines · 38 tokens per session scan A d454138768cd

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository affaan-m/ECC (280,368 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 2,038 once invoked, about $0.0002 per session on Opus 5.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.