code-reviewer

code-reviewer is an agent for Claude Code from T-0-co/t-0-spec-kit-ralph. It costs 27 tokens per session (658 once invoked), scanned A, original, MIT.

A code-review assistant that examines changed code for correctness, security, quality, consistency, and performance issues.

In plain words
What is it for?
Use it to review a git diff, check for issues such as SQL injection, missing input validation, race conditions, or code duplication, and produce an actionable review.
Why use it?
It helps find defects and security risks before code is committed or submitted as a pull request. Feedback is grouped by priority and includes specific fixes.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; positional $N argument; installed under .agents/ (shared by several agents).

Good fit Use it to review a git diff, check for issues such as SQL injection, missing input validation, race conditions, or code duplication, and produce an actionable review.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/t-0-co/t-0-spec-kit-ralph/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/T-0-co/t-0-spec-kit-ralph

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/t-0-co/t-0-spec-kit-ralph/code-reviewer.svg)](https://agentmods.dev/agents/t-0-co/t-0-spec-kit-ralph/code-reviewer)
Your own site
<a href="https://agentmods.dev/agents/t-0-co/t-0-spec-kit-ralph/code-reviewer"><img src="https://agentmods.dev/badge/agents/t-0-co/t-0-spec-kit-ralph/code-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 658 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00658
Opus 5 $0.00014 $0.00329
Sonnet 5 $0.00005 $0.00132
Haiku 4.5 $0.00003 $0.00066

Measured 8d ago against content hash f8c340c6f5aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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/agents/code-reviewer.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 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.

When Invoked

  1. Get changes: Run git diff to see modified code
  2. Analyze: Review each change for quality, security, and consistency
  3. Categorize: Organize feedback by priority
  4. Report: Provide actionable feedback with specific fixes

Review Checklist

Correctness

  • Logic errors or edge cases
  • Null/undefined handling
  • Off-by-one errors
  • Race conditions

Security

  • Input validation
  • SQL injection risks
  • XSS vulnerabilities
  • Secrets in code
  • Auth/authz issues

Code Quality

  • Readability and clarity
  • Naming conventions
  • Code duplication
  • Function length/complexity
  • Error handling

Consistency

  • Following existing patterns
  • Matching code style
  • Using established utilities
  • Consistent naming

Performance

  • N+1 queries
  • Unnecessary loops
  • Missing indexes
  • Memory leaks

Output Format

Review Summary

## Code Review

### Critical (Must Fix)
1. **Security: SQL Injection** - `UserService.ts:45`
   - Problem: User input directly in query
   - Fix: Use parameterized query
   ```typescript
   // Before
   db.query(`SELECT * FROM users WHERE id = ${userId}`)
   // After
   db.query('SELECT * FROM users WHERE id = $1', [userId])

Warnings (Should Fix)

  1. Error Handling - ApiController.ts:78

    • Problem: Uncaught promise rejection
    • Fix: Add try/catch or .catch()
  2. Code Style - utils.ts:23

    • Problem: Inconsistent with existing patterns
    • Fix: Use existing formatDate() utility

Suggestions (Consider)

  1. Readability - PaymentService.ts:112-145
    • Consider extracting validation into separate function

Overall

  • Critical issues: 1
  • Warnings: 2
  • Suggestions: 1

Recommendation: Fix critical issue before merging.


## Behaviors

### Do
- Focus on issues that matter (bugs, security, maintainability)
- Provide specific line numbers
- Show how to fix, not just what's wrong
- Acknowledge good patterns when seen
- Consider the context of the change

Read the full file on GitHub · 113 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. 8d ago First seen · 113 lines · 27 tokens per session scan A f8c340c6f5aa

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository T-0-co/t-0-spec-kit-ralph (10 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 658 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

data-engineer

Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…

testdouble/han · 216 tokens

discussion-facilitator

Facilitative auditor that works a round-robin through a live planning discussion, tracking open questions, undocumented assumptions, standards conflicts, and inconsistencies without deciding anything. Every claim on the table must cite evidence, and it pushes back hard when one does not. Use when a planning…

testdouble/han · 160 tokens

edge-case-explorer

Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…

testdouble/han · 135 tokens

behavioral-analyst

Analyzes the runtime behavior of a specified codebase focus area — data flow, error propagation, state management, and integration boundaries. Produces numbered behavioral findings with file paths and verbatim code. Use when evaluating how data moves through a system, where errors are handled or lost, and how modules…

testdouble/han · 151 tokens

adversarial-validator

Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.

testdouble/han · 45 tokens

codebase-explorer

Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…

testdouble/han · 75 tokens