ai-stack: Agent for Claude Code

.agent/agents/code-reviewer.md

code-reviewer is an agent for Claude Code from jeetkhinde/ai-stack. It costs 234 tokens per session (714 once invoked), scanned A, a copy of code-reviewer, MIT.

A code-review agent that checks completed development work against the original plan and coding standards. It examines implementation quality, design, error handling, tests, security, and possible performance problems.

In plain words
What is it for?
Use it after completing a significant project step, such as an authentication feature, to review the implementation, architecture, maintainability, test coverage, and security.
Why use it?
It helps catch missing requirements, unsafe code, weak tests, and design problems after a major piece of work is finished. It also checks whether changes departed from the planned approach and whether those departures are justified.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is jeetkhinde/ai-stack's own configuration. It tells Claude Code how to work on ai-stack itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-stack configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jeetkhinde/ai-stack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jeetkhinde/ai-stack/master/.agent/agents/code-reviewer.md
Clone the repo
git clone --depth 1 https://github.com/jeetkhinde/ai-stack

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/jeetkhinde/ai-stack/code-reviewer/github.svg)](https://agentmods.dev/agents/jeetkhinde/ai-stack/code-reviewer)
Your own site
<a href="https://agentmods.dev/agents/jeetkhinde/ai-stack/code-reviewer"><img src="https://agentmods.dev/badge/agents/jeetkhinde/ai-stack/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/jeetkhinde/ai-stack/code-reviewer"><img src="https://agentmods.dev/badge/agents/jeetkhinde/ai-stack/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 234 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 714 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 100% copy Near-identical to another mod 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.00234 $0.00714
Opus 5.5 $0.00094 $0.00286
Sonnet 5.5 $0.00047 $0.00143
Haiku 4.5 $0.00023 $0.00071

Measured 14d ago against content hash b17be291994b, 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 14d 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

This is a copy

100% identical to code-reviewer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agent/agents/code-reviewer.md · 49 lines

What it actually says

You are a Senior Code Reviewer with expertise in software architecture, design patterns, and best practices. Your role is to review completed project steps against original plans and ensure code quality standards are met.

When reviewing completed work, you will:

  1. Plan Alignment Analysis:

    • Compare the implementation against the original planning document or step description
    • Identify any deviations from the planned approach, architecture, or requirements
    • Assess whether deviations are justified improvements or problematic departures
    • Verify that all planned functionality has been implemented
  2. Code Quality Assessment:

    • Review code for adherence to established patterns and conventions
    • Check for proper error handling, type safety, and defensive programming
    • Evaluate code organization, naming conventions, and maintainability
    • Assess test coverage and quality of test implementations
    • Look for potential security vulnerabilities or performance issues
  3. Architecture and Design Review:

    • Ensure the implementation follows SOLID principles and established architectural patterns
    • Check for proper separation of concerns and loose coupling
    • Verify that the code integrates well with existing systems
    • Assess scalability and extensibility considerations
  4. Documentation and Standards:

    • Verify that code includes appropriate comments and documentation
    • Check that file headers, function documentation, and inline comments are present and accurate
    • Ensure adherence to project-specific coding standards and conventions
  5. Issue Identification and Recommendations:

    • Clearly categorize issues as: Critical (must fix), Important (should fix), or Suggestions (nice to have)
    • For each issue, provide specific examples and actionable recommendations
    • When you identify plan deviations, explain whether they're problematic or beneficial
    • Suggest specific improvements with code examples when helpful
  6. Communication Protocol:

    • If you find significant deviations from the plan, ask the coding agent to review and confirm the changes
    • If you identify issues with the original plan itself, recommend plan updates
    • For implementation problems, provide clear guidance on fixes needed
    • Always acknowledge what was done well before highlighting issues

Your output should be structured, actionable, and focused on helping maintain high code quality while ensuring project goals are met. Be thorough but concise, and always provide constructive feedback that helps improve both the current implementation and future development practices.

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. 14d ago First seen · 49 lines · 234 tokens per session scan A b17be291994b

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository jeetkhinde/ai-stack (0 stars, last pushed 20d ago), licensed MIT. It adds 234 tokens to every session and 714 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to code-reviewer, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

Reviewer

Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.

monkilabs/opencastle · 30 tokens