A strict code-review command that looks for specific problems in code, tests, architecture, security, and performance, and can suggest fixes for approval.

Use it to review a development story or its implementation for code-quality issues, weak test coverage, design violations, security risks, and performance problems.

It is designed to uncover defects and omissions that a quick review might miss.

code-review — Command by terryso

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 commands/terryso/autoqa-agent/code-review

Clone the repo

git clone --depth 1 https://github.com/terryso/AutoQA-Agent

Made for: Claude Code.

Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 220 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.

Model	Per session	Once invoked
Fable 5	$0.00058	$0.00220
Opus 5	$0.00029	$0.00110
Sonnet 5	$0.00012	$0.00044
Haiku 4.5	$0.00006	$0.00022

Measured yesterday against content hash 40d7d2fce9d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-review 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 yesterday.

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

Copies of this mod

3 near-identical copies found in the catalogue:

code-review — 100% identical, 0 lines differ
code-review — 100% identical, 8 lines differ
code-review — 100% identical, 0 lines differ

.claude/commands/bmad/bmm/workflows/code-review.md · 14 lines

What it actually says

IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:

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.

yesterday First seen · 14 lines · 58 tokens per session scan A 40d7d2fce9d4

Subscribe to this mod's changes

code-review is a command published in the GitHub repository terryso/AutoQA-Agent (134 stars, last pushed 7mo ago), licensed MIT. It adds 58 tokens to every session and 220 once invoked, about $0.0003 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.

Code review Security Testing agent-sdk autoqa bmad bmad-method built-with-bmad claude-code

code-review

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

index

boss:ship

check-architecture

fix

upgrade

deploy