Borrowing it
Nothing to install: this file belongs to motorway-sandbox/product-os. 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/motorway-sandbox/product-os/main/.claude/commands/review-design.mdgit clone --depth 1 https://github.com/motorway-sandbox/product-osWrote 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/motorway-sandbox/product-os/review-design)<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/review-design"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/review-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/review-design"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/review-design.svg" alt="Reviewed on agentmods" width="80" 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.03474 |
| Opus 5.5 | $0.00000 | $0.01390 |
| Sonnet 5.5 | $0.00000 | $0.00695 |
| Haiku 4.5 | $0.00000 | $0.00347 |
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 2mo 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Review
Review design screenshots against your product frameworks and save a structured, evidence-based review.
Arguments: $ARGUMENTS (optional — the hypothesis being tested)
Instructions
Phase 1: Gather Context
-
Check for images. If no design screenshots are visible in the conversation, ask the user to paste them before continuing. Do not proceed without images.
-
Parse the hypothesis. If
$ARGUMENTScontains text, use it as the hypothesis. If it is empty or missing, ask: "What hypothesis is this design testing? (If/then/because format is ideal, but a plain description works too.)" -
Determine context. Ask the user (if not obvious from the designs):
- Is this customer-facing or internal/B2B-facing?
- What journey stage does this sit in? (e.g. onboarding, checkout, post-purchase, admin dashboard)
- Is there an existing project file this relates to? (e.g. a file in
projects/)
-
Read reference files silently (do not output their contents). Always read:
context/product.mddata/funnel-context.mdcontext/brand/messaging/how-we-sound.mdcontext/brand/messaging/our-language.mdpm-playbook/process/4-design.md
If relevant, also read:
strategy/activation/activation-strategy.md(Note: this is a DRAFT document — use its frameworks as reference but do not treat its specific recommendations as validated or current strategy)context/personas/customer-personas.md
For B2B/partner-facing features, also read:
strategy/activation/partner-activation-strategy.md(Note: this is a DRAFT document — same caveat as above)context/personas/partner-personas.md
If a project file was identified, also read it.
Phase 2: Analyse (6 Lenses)
Work through all six lenses below. Do not skip any.
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.
- 2mo ago First seen · 266 lines · 0 tokens per session scan A 317b5ae4a8f2
review-design is a command published in the GitHub repository motorway-sandbox/product-os (11 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,474 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-09-04.
review-design compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| review-designmotorway-sandbox/product-os | Command | 11 | 5mo ago | MIT | A | 0 | Claude Code |
| profilecathrynlavery/diagram-design | Command | 65k | 3d ago | MIT | A | 16 | Claude Code |
| erne-animateJubaKitiashvili/everything-react-native-expo | Command | 50 | 29d ago | MIT | A | 21 | Claude Code |
| ui-flow-reviewMRCalderon3D/everything-game-dev-code | Command | 104 | 28d ago | MIT | A | 15 | Claude Code |
| responsive-design-specialistimsaif/design-with-claude | Command | 11 | yesterday | MIT | A | 36 | Claude Code |
| design-auditw2ur/claude-code-setup | Command | 2 | 3d ago | MIT | A | 30 | Claude Code |
| ppt-image2-editable-rebuildwwe-dog/ppt-image2-editable-rebuild | Command | 204 | 5mo ago | Unlicense | A | 15 | Claude Code |