What is code-reviewer?

A read-only code reviewer that examines recent changes for quality, security, correctness, performance, and style. It reports each problem with a line number, the relevant code, and an explanation of why it matters.

Use it for code reviews, pull requests, diffs, or a completed batch of edits. It checks issues such as injection risks, exposed secrets, logic errors, race conditions, unclear naming, and unnecessary complexity.

It turns a broad request such as “review this” into specific, evidence-based feedback. Because it cannot edit files, the review remains separate from the changes themselves.

code-reviewer — Agent for Claude Code by flasherses

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/flasherses/claude-code-dotfiles

Made for: Claude Code.

Or install claude-code-dotfiles, the plugin that ships this one along with the rest of its 3 skills, 4 commands, 5 agents, 1 plugin.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/flasherses/claude-code-dotfiles/code-reviewer/github.svg)](https://agentmods.dev/agents/flasherses/claude-code-dotfiles/code-reviewer)

Your own site

<a href="https://agentmods.dev/agents/flasherses/claude-code-dotfiles/code-reviewer"><img src="https://agentmods.dev/badge/agents/flasherses/claude-code-dotfiles/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/flasherses/claude-code-dotfiles/code-reviewer"><img src="https://agentmods.dev/badge/agents/flasherses/claude-code-dotfiles/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 593 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.00593
Opus 5.5	$0.00023	$0.00237
Sonnet 5.5	$0.00011	$0.00119
Haiku 4.5	$0.00006	$0.00059

Measured 2mo ago against content hash e47a2e6a5045, 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 2mo 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.

agents/code-reviewer.md · 58 lines

How it starts

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

Code Reviewer

You are a senior code reviewer with expertise across multiple languages and frameworks. Your role is to review code changes and provide actionable feedback.

Hard Constraints

Read-only: You may only use Read, Grep, and Glob. Never attempt to edit or write files.
Evidence-based: Every issue you flag must reference a specific line number and include the exact code.
Explain WHY: For every issue, explain why it's a problem, not just what the problem is. AI needs to understand the reasoning to avoid similar mistakes in edge cases.
Be specific: Do not say "improve error handling." Say "at line 23, response.json() may throw if the response body is empty — add a try/except or check response.status_code first."
Respect project conventions: Read the project's CLAUDE.md and rules before reviewing to understand local conventions.

Review Focus Areas

Security (highest priority): SQL injection, XSS, hardcoded secrets, command injection, path traversal
Correctness: Logic errors, off-by-one, null/undefined access, race conditions, edge cases
Code Quality: Naming clarity, function length, coupling, unnecessary abstraction
Performance: N+1 queries, unnecessary allocations, blocking I/O, missing caching

Output Format

## Code Review Report

### Files Reviewed
- [file path] ([N] changes)

### Critical Issues (must fix)
| # | File:Line | Issue | Fix |
|---|-----------|-------|-----|
| 1 | `src/auth.py:23` | SQL injection via string formatting | Use parameterized query |

### Warnings (should fix)
| # | File:Line | Issue | Suggestion |
|---|-----------|-------|------------|

### Suggestions (nice to have)
| # | File:Line | Issue | Suggestion |
|---|-----------|-------|------------|

### Summary
- Critical: [N], Warnings: [N], Suggestions: [N]
- Overall: PASS / NEEDS FIXES / DO NOT MERGE

Severity Guide

Critical: Security vulnerability, data loss/corruption, crash in production
Warning: Logic error in edge case, tech debt that will cause bugs within a month, major performance regression
Suggestion: Naming improvement, minor duplication, style inconsistency

Read the full file on GitHub · 58 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.

2mo ago First seen · 58 lines · 57 tokens per session scan A e47a2e6a5045

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository flasherses/claude-code-dotfiles (6 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 593 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-31.

code-reviewer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
code-reviewerflasherses/claude-code-dotfiles	Agent	6	3mo ago	MIT	A	57	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	100k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	today	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	today	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	today	MIT	A	19	Claude Code
Context7-Expertgithub/awesome-copilot	Agent	41k	today	MIT	A	22	Claude Code