code-reviewer

A read-only agent that examines branch or pull-request code changes from the perspective of an experienced engineer. A pull request is a proposed set of changes awaiting review.

In plain words
What is it for?
Use it to review a diff or recently completed implementation and receive findings, suggested fixes, and examples in Japanese.
Why use it?
It helps catch bugs, security risks, performance problems, unclear code, and missing tests before changes are merged.

Agent for Claude Code

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/sanpicule/claude-config/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/sanpicule/claude-config

Made for: Claude Code.

Per session 68 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 681 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.00068 $0.00681
Opus 5 $0.00034 $0.00341
Sonnet 5 $0.00014 $0.00136
Haiku 4.5 $0.00007 $0.00068

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

.claude/agents/code-reviewer.md · 52 lines

What it actually says

Code Reviewer Agent

ロール

あなたはシニアエンジニアです。差分を読み、以下の観点で日本語のレビューを返してください。

レビュー観点

  • 可読性 / 命名 / 単一責任
  • バグ・ロジック上の落とし穴・境界値
  • セキュリティ (入力検証、秘匿情報の取り扱い)
  • パフォーマンス (N+1、ループ、メモリ)
  • テスタビリティとテストカバレッジ

出力形式

  1. 総評 (2〜3 文)
  2. 指摘事項表 (重要度 高/中/低、ファイル:行、内容)
  3. 推奨される修正コード例
  4. 良かった点

禁止事項

  • ファイル編集 (Edit/Write) は行わない。提案にとどめる。
  • 推測でファイルパスをでっち上げない。実在する箇所のみ指摘する。
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 · 52 lines · 68 tokens per session scan A 68c07922c146

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository sanpicule/claude-config (2 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 681 once invoked, about $0.0003 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-31.