Borrowing it
Nothing to install: this file belongs to dsifry/metaswarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dsifry/metaswarm/main/.claude/commands/review-design.mdgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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.
[](https://agentmods.dev/commands/dsifry/metaswarm/review-design)<a href="https://agentmods.dev/commands/dsifry/metaswarm/review-design"><img src="https://agentmods.dev/badge/commands/dsifry/metaswarm/review-design.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00000 | $0.01009 |
| Opus 5 | $0.00000 | $0.00504 |
| Sonnet 5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
review-design 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Design Command
Run the design review gate on a design document to get feedback from Product Manager, Architect, Designer, Security Design, and CTO agents.
Usage
/review-design <path-to-design-doc>
Examples
# Review a specific design document
/review-design docs/plans/2026-01-11-contact-assistant-design.md
# Review the most recent design document
/review-design --latest
# Re-run review after revisions
/review-design docs/plans/2026-01-11-contact-assistant-design.md --iteration 2
What This Does
- Validates the design document exists and is in the expected format
- Spawns five review agents in parallel:
- Product Manager Agent - Validates use cases and user benefits
- Architect Agent - Reviews technical architecture
- Designer Agent - Reviews UX, API design, developer experience
- Security Design Agent - Reviews security threats and mitigations
- CTO Agent - Reviews TDD readiness, codebase alignment
- Aggregates results from all five agents
- Reports outcome with blockers, suggestions, and next steps
Arguments
| Argument | Description |
|---|---|
<path> |
Path to design document (required unless --latest) |
--latest |
Review most recent design doc in docs/plans/ |
--iteration N |
Mark as iteration N of review cycle |
--skip-agent <name> |
Skip specific agent (pm, architect, designer, security, cto) |
Review Verdicts
APPROVED
All agents approve. Output includes:
- Summary of what each agent reviewed
- Non-blocking suggestions for future improvement
- Next steps for implementation
NEEDS_REVISION
One or more agents found blocking issues. Output includes:
- List of blocking issues by agent
- Questions requiring clarification
- Iteration count (max 3 before escalation)
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.
- 7d ago First seen · 181 lines · 0 tokens per session scan A 962d567c1c2b
review-design is a command published in the GitHub repository dsifry/metaswarm (413 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,009 tokens. 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.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.