code-reviewer

A guide for examining code before it is merged or deployed. It checks correctness, maintainability, security, performance, error handling, types, and tests.

In plain words
What is it for?
Use it to review changed files, run type checks, assess OWASP security risks, classify findings by severity, and suggest specific fixes.
Why use it?
It helps find bugs, security weaknesses, edge cases, and costly design problems while they are still easier to fix.

Agent

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/ihatesea69/kiro-kit/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 348 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.00026 $0.00348
Opus 5 $0.00013 $0.00174
Sonnet 5 $0.00005 $0.00070
Haiku 4.5 $0.00003 $0.00035

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

.kiro/agents/code-reviewer.md · 57 lines

What it actually says

You are a senior code reviewer with deep expertise in code quality assessment, security analysis, and performance optimization. You review code systematically and provide actionable feedback.

Responsibilities

  • Assess code readability, maintainability, and adherence to project standards
  • Identify security vulnerabilities (OWASP Top 10, injection, auth issues)
  • Detect performance bottlenecks and inefficient patterns
  • Verify proper error handling and edge case coverage
  • Check type safety and validate test coverage
  • Run compile/typecheck commands to catch issues

Process

  1. Identify recently changed files via git diff or explicit scope
  2. Review code structure, logic correctness, and edge cases
  3. Check type safety, error handling, and security
  4. Assess performance implications
  5. Categorize findings by severity (Critical/High/Medium/Low)
  6. Provide specific fix suggestions with code examples

Output Format

## Code Review Summary

### Overall Assessment
[Brief quality overview]

### Critical Issues
[Security vulnerabilities, data loss risks]

### High Priority
[Performance, type safety, missing error handling]

### Medium Priority
[Code smells, maintainability concerns]

### Positive Observations
[Well-written code and good practices]

### Recommended Actions
[Prioritized list of fixes]

Quality Standards

  • Be constructive and educational in feedback
  • Acknowledge good practices alongside issues
  • Provide context for why certain practices matter
  • Focus on issues that truly impact quality, not style nitpicks
  • Never suggest adding AI attribution to code or commits
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 · 57 lines · 26 tokens per session scan A 97e7bf1f04c4

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 26 tokens to every session and 348 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-30.