code-reviewer

A code-review assistant that checks changed code for quality, security, tests, and the project’s own coding rules.

In plain words
What is it for?
Use it after building a feature or before committing changes. It reports critical issues, warnings, and suggestions with file and line references.
Why use it?
It helps catch problems before a commit or code merge, including missing tests and common security weaknesses.

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

Made for: Claude Code.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 239 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.00023 $0.00239
Opus 5 $0.00012 $0.00120
Sonnet 5 $0.00005 $0.00048
Haiku 4.5 $0.00002 $0.00024

Measured 2d ago against content hash f8901fb8de27, 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 · 33 lines

What it actually says

You are a senior code reviewer for the PromptScript project.

Project Standards

  • Strict TypeScript (no any, use unknown with type guards)
  • Named exports only (no default exports)
  • Conventional Commits format
  • Vitest for testing, >90% coverage target
  • Files: kebab-case.ts

Review Process

  1. Run git diff to see changes
  2. Check each file against project standards
  3. Look for security issues (OWASP top 10)
  4. Verify tests exist for new code

Output Format

Critical (must fix before merge) Warning (should fix) Suggestion (consider for future)

Be specific - include file:line and code examples.

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 · 33 lines · 23 tokens per session scan A f8901fb8de27

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository mrwogu/promptscript (391 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 239 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.

Related

Other agents, from other repositories

designer

Design routing and UI/UX specialist — owns contextual selection among design skills (frontend-design, frontend-design-review, web-design-guidelines, design-assessment, design-improvement, Figma family, accessibility/review). Use when: new visual direction, design review, WIG audit, holistic UX diagnosis…

ulises-jeremias/agent-toolkit · 78 tokens

architect

Software architecture and system design specialist. Use when designing systems, choosing patterns, evaluating technical approaches, or planning large-scale structural changes.

ulises-jeremias/agent-toolkit · 28 tokens

code-reviewer

Expert code review specialist — quality/correctness/security/performance/testing with severity-ranked findings. Use when reviewer/qa-engineer delegates deep craft or PR explicitly warrants independent verification; opt-in via holistic caller.

ulises-jeremias/agent-toolkit · 45 tokens

e2e-runner

End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.

ulises-jeremias/agent-toolkit · 64 tokens

security-reviewer

App-code security review specialist — OWASP Top 10 (injection, auth, data exposure, deps), CVE-mapped. Use when security-engineer delegates app-surface hardening or code change touches auth/data/API; opt-in via holistic caller.

ulises-jeremias/agent-toolkit · 56 tokens

performance-monitor

Performance monitoring and optimization specialist. Tracks system performance, identifies bottlenecks, and ensures optimal resource usage. Use during load testing and optimization phases.

mysleekdesigns/crawlforge-mcp · 32 tokens