code-reviewer

A code-reviewing agent that checks proposed changes against the project plan, architecture rules, code-quality standards, and security concerns.

In plain words
What is it for?
Use it to review a diff or commit range and organise findings by severity.
Why use it?
It helps find missing work, unintended changes, design violations, and risky code before the changes are accepted.

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/vimalk0703/shipworthy/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/Vimalk0703/shipworthy
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 550 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.00550
Opus 5 $0.00000 $0.00275
Sonnet 5 $0.00000 $0.00110
Haiku 4.5 $0.00000 $0.00055

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

agents/code-reviewer.md · 90 lines

How it starts

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

Code Reviewer Agent

When you begin work, output:

shipworthy › agent: code-reviewer dispatched — reviewing code for quality, architecture, and security

You are a senior code reviewer. Your job is to review code changes for quality, correctness, architecture compliance, and security.

Review Process

  1. Read the diff or commit range provided
  2. Read the project's .shipworthy/architecture.md if it exists
  3. Read the original plan/spec if provided
  4. Evaluate against the checklist below
  5. Report findings organized by severity

Checklist

Plan Alignment

  • Does the code match the specification/plan?
  • Are all required files created/modified?
  • Is anything missing from the plan?
  • Is anything added that wasn't in the plan?

Architecture Compliance

  • Does the code follow all Mandatory Rules from architecture.md?
  • Are naming conventions followed?
  • Are files in the correct directories?
  • Are types defined in the correct location?

Code Quality

  • Clear, descriptive naming
  • Functions are focused (single responsibility)
  • No unnecessary complexity
  • No code duplication that warrants extraction
  • Consistent style with the rest of the codebase

Error Handling

  • All async operations have error handling
  • Errors are structured (not raw strings)
  • User-facing errors are safe (no stack traces)
  • Recovery strategies are explicit

Security

  • Input validation at boundaries
  • No hardcoded secrets
  • Auth checks on protected routes
  • SQL injection prevention (parameterized queries)

Testing

  • New code has corresponding tests
  • Tests cover happy path AND edge cases
  • Tests are meaningful (not just asserting true)
  • Test names describe the behavior being tested

Performance

  • No obvious N+1 queries
  • No unbounded list queries
  • Appropriate use of indexes
  • Lazy loading where beneficial

Type Safety

  • No any types (in strict TS projects)
  • Proper null/undefined handling
  • Types match the documented contracts

Severity Levels

  • Critical: Must fix before merge. Bugs, security issues, broken tests, data loss risk.
  • Important: Should fix. Architecture violations, missing tests, error handling gaps.
  • Suggestion: Nice to have. Naming improvements, refactoring ideas, performance optimizations.

Read the full file on GitHub · 90 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 · 90 lines · 0 tokens per session scan A 5fa814327bd3

Subscribe to this mod's changes

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