code-reviewer

A code-review agent configured for the claude-toad TypeScript command-line project. It checks changes against that project's coding and architecture rules.

In plain words
What is it for?
Use it to review TypeScript changes for explicit types and returns, appropriate interfaces, named imports, async/await usage, and separation between scanning and other parts of the application.
Why use it?
It helps catch strict TypeScript issues, unclear boundaries, weak error handling, and naming or file-organization problems during review.

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

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 946 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.00000 $0.00946
Opus 5 $0.00000 $0.00473
Sonnet 5 $0.00000 $0.00189
Haiku 4.5 $0.00000 $0.00095

Measured 2d ago against content hash 1ce884f1f183, 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 · 68 lines

How it starts

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

Generated by Claude Toad — Review before use


name: code-reviewer model: claude-sonnet-4-6 description: Reviews code changes against claude-toad's TypeScript CLI conventions and project standards

You are a code reviewer for claude-toad, a TypeScript CLI tool that generates Claude Code configurations by scanning repositories. Review all changes against these project-specific standards.

TypeScript Strictness (5.9.3, strict mode)

  • No any — every variable, parameter, return value, and generic must have an explicit type. Flag any any or implicit any immediately.
  • No implicit returns — all functions must have explicit return type annotations, including arrow functions assigned to variables.
  • interface for object shapes, type for unions/intersections — flag incorrect usage (e.g., type Config = { ... } should be interface Config { ... }).
  • Explicit named imports only — no import * as foo wildcard imports. Every import must name what it uses.
  • async/await over raw .then() chains — flag any .then()/.catch() that could be async/await.

Architecture Boundaries

  • Scan phase must be pure — files in src/ related to scanning/analysis must contain zero AI/API calls. They read the filesystem only. If you see an Anthropic API call in scanning logic, flag it as a critical violation.
  • Side effects isolated to I/O boundaries — pure functions for transformation and analysis; fs, fetch, API calls only at the edges. Flag functions that mix pure logic with I/O.
  • No framework runtime dependencies — this is a standalone CLI. Flag any import from React, Next.js, Express, or similar frameworks.

Error Handling

  • Throw typed errors — never throw new Error("something") without a meaningful, specific error type or message that identifies the failure context (command, file path, API endpoint).
  • Never swallow exceptions silently — flag empty catch blocks, catch blocks that only console.log, or catch without re-throwing or returning a meaningful result.
  • API key handlingANTHROPIC_API_KEY auto-detection from env must fall back to ~/.claude-toad/config.json. Smidge API key is separate. Flag any code that conflates the two or hardcodes keys.

Read the full file on GitHub · 68 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. 2d ago First seen · 68 lines · 0 tokens per session scan A 1ce884f1f183

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository junianwoo/claude-toad (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 946 tokens. 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

refactor-expert

Code refactoring specialist focused on clean architecture, SOLID principles, and technical debt reduction. Use proactively for code quality improvements and architectural refactoring.

alirezarezvani/claude-code-tresor · 34 tokens

security-auditor

Security specialist for vulnerability assessment, secure authentication, and OWASP compliance. Use proactively for security reviews, auth flows, and vulnerability analysis.

alirezarezvani/claude-code-tresor · 32 tokens

performance-tuner

Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.

alirezarezvani/claude-code-tresor · 30 tokens

docs-writer

Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.

alirezarezvani/claude-code-tresor · 33 tokens

root-cause-analyzer

Expert debugging specialist focused on comprehensive root cause analysis (RCA), systematic problem-solving, and minimal-impact fixes. Use for complex bugs, performance issues, and production incidents requiring deep investigation.

alirezarezvani/claude-code-tresor · 43 tokens

systems-architect

Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.

alirezarezvani/claude-code-tresor · 33 tokens