review

A command that reviews recent code changes for quality, security vulnerabilities, and common development practices.

In plain words
What is it for?
Use it after making code changes to get actionable review findings and suggested improvements.
Why use it?
It helps find problems in a change before they reach other developers or users, with feedback sorted by priority.

Command

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/webdevtodayjason/sub-agents/review
Clone the repo
git clone --depth 1 https://github.com/webdevtodayjason/sub-agents
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 55 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.00055
Opus 5 $0.00004 $0.00028
Sonnet 5 $0.00002 $0.00011
Haiku 4.5 $0.00001 $0.00006

Measured 2d ago against content hash 15754d90a845, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

Origin

This is a copy

100% identical to review — 1 line 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.

commands/review.md · 7 lines

What it actually says

Use the code-reviewer agent to perform a comprehensive code review on recent changes. Focus on code quality, security vulnerabilities, and best practices. Provide actionable feedback organized by priority.

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 · 7 lines · 8 tokens per session scan A 15754d90a845

Subscribe to this mod's changes

review is a command published in the GitHub repository webdevtodayjason/sub-agents (201 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 55 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review, differing in 1 line, and is treated as a copy.