review

review is a command for coding agents from gerard-labs/superpowers-api-platform. It costs 40 tokens per session (502 once invoked), scanned A, original, MIT.

A code-review command for Symfony and API Platform changes. It checks the code against a detailed list of design, security, testing, and framework rules, then issues an approval or change request.

In plain words
What is it for?
Use it after implementation and testing to classify a diff, check security concerns and anti-patterns, and produce a documented review verdict.
Why use it?
It gives reviewers a consistent checklist and records the evidence behind the decision. This reduces unsupported claims and missed problems before changes are accepted.

Command

Part of the gerard plugin — 25 skills, 25 commands, 7 agents, 1 hook shipped together

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/gerard-labs/superpowers-api-platform/review
Clone the repo
git clone --depth 1 https://github.com/gerard-labs/superpowers-api-platform

Or install gerard, the plugin that ships this one along with the rest of its 25 skills, 25 commands, 7 agents, 1 hook.

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/gerard-labs/superpowers-api-platform/review.svg)](https://agentmods.dev/commands/gerard-labs/superpowers-api-platform/review)
Your own site
<a href="https://agentmods.dev/commands/gerard-labs/superpowers-api-platform/review"><img src="https://agentmods.dev/badge/commands/gerard-labs/superpowers-api-platform/review.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 502 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.00040 $0.00502
Opus 5 $0.00020 $0.00251
Sonnet 5 $0.00008 $0.00100
Haiku 4.5 $0.00004 $0.00050

Measured 4d ago against content hash 69034c73de86, 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 4d 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.

commands/review.md · 38 lines

What it actually says

You are the Review stage coordinator. Inputs:

  • .claude/last-api-plan.md
  • .claude/last-api-dev-report.md
  • .claude/last-api-test-report.md

Step 1 — Read all state files

The reviewer MUST have full context for an auditable verdict.

Step 2 — Invoke symfony-reviewer via Task

The reviewer MUST:

  1. Read all 3 state files
  2. Emit diff classification preamble (Diff type / API Platform area / Operation type / Surface)
  3. Emit ===EVIDENCE=== block (skills dispatched, diff size, commands run, state files read, anti-patterns checklist tally, AppSec bilan from plan)
  4. Apply the 24+ anti-patterns checklist (16 API Platform 4.3 + 8 Symfony 7.4+ + tests + appsec)
  5. Cap unverified claims (any "I ran X" must have a tool call in this session)
  6. Detect skill-dispatch theatre (claimed skill dispatches must have actual Task/Skill calls)
  7. Emit verdict between ===API-REVIEW-BEGIN=== / ===API-REVIEW-END===. First non-empty line MUST be exactly VERDICT: APPROVE or VERDICT: REQUEST_CHANGES.
  8. On APPROVE: mandatory **Out of scope for this review:** section.
  9. On REQUEST_CHANGES: numbered findings (file:line + rule # + change required).

Step 3 — Persist state file

Write .claude/last-api-review.md with the full content between ===API-REVIEW-BEGIN=== and ===API-REVIEW-END=== (exclude markers themselves).

Step 4 — Surface to user

  • On APPROVE: notify "Verdict: APPROVE. Diff ready in working tree. Inspect with git diff or run /api-resource-pipeline / /api-resource-ship for the chained flow."
  • On REQUEST_CHANGES: surface the numbered findings. User can re-run /dev to address them (or the chain commands do it automatically).
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. 4d ago First seen · 38 lines · 40 tokens per session scan A 69034c73de86

Subscribe to this mod's changes

review is a command published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 502 once invoked, about $0.0002 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-31.