review

review is a command for Claude Code from klh/speedy-claude. It costs 16 tokens per session (247 once invoked), scanned A, a copy of review, MIT.

A command for reviewing code changes across correctness, readability, architecture, security, and performance.

In plain words
What is it for?
Reviewing staged changes or recent commits, categorising findings by severity, and giving file-and-line-specific recommendations.
Why use it?
It provides a structured way to find defects, unclear code, design problems, security risks, and slow operations before they reach users.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Reviewing staged changes or recent commits, categorising findings by severity, and giving file-and-line-specific recommendations.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/klh/speedy-claude/review
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.

Clone the repo
git clone --depth 1 https://github.com/klh/speedy-claude

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review

README.md
[![agentmods](https://agentmods.dev/badge/commands/klh/speedy-claude/review.svg)](https://agentmods.dev/commands/klh/speedy-claude/review)
Your own site
<a href="https://agentmods.dev/commands/klh/speedy-claude/review"><img src="https://agentmods.dev/badge/commands/klh/speedy-claude/review.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 247 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00016 $0.00247
Opus 5 $0.00008 $0.00123
Sonnet 5 $0.00003 $0.00049
Haiku 4.5 $0.00002 $0.00025

Measured 3d ago against content hash 6c12be9aef27, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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 3d 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 — 16 lines 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 · 21 lines

What it actually says

For deep reviews, dispatch the code-reviewer persona (and security-auditor for security-critical changes). Mechanical pass first:

qlty check            # diff-aware: only your branch's changes
difft main...HEAD     # structural diff — moves/renames render correctly

Review the current changes (staged or recent commits) across all five axes:

  1. Correctness — Does it match the spec? Edge cases handled? Tests adequate?
  2. Readability — Clear names? Straightforward logic? Well-organized?
  3. Architecture — Follows existing patterns? Clean boundaries? Right abstraction level? (Event mediator/composition over inheritance; close to the metal)
  4. Security — Input validated? Secrets safe? Auth checked? (dispatch security-auditor for auth/crypto/input changes)
  5. Performance — No N+1 queries? No unbounded ops?

Categorize findings as Critical, Important, or Suggestion. Output a structured review with specific file:line references and fix recommendations. Every Critical/Important finding includes the fix.

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. 3d ago Changed · +4 lines 6c12be9aef27
  2. 7d ago First seen · 17 lines · 16 tokens per session scan A 8ad7da75873b

Subscribe to this mod's changes

review is a command published in the GitHub repository klh/speedy-claude (11 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 247 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review, differing in 16 lines, and is treated as a copy.