Borrowing it
Nothing to install: this file belongs to basher83/lunar-claude. 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/basher83/lunar-claude/main/.claude/commands/design-validation/self-critique-design-review.mdgit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/basher83/lunar-claude/self-critique-design-review)<a href="https://agentmods.dev/commands/basher83/lunar-claude/self-critique-design-review"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/self-critique-design-review/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/basher83/lunar-claude/self-critique-design-review"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/self-critique-design-review.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.00007 | $0.01281 |
| Opus 5 | $0.00003 | $0.00641 |
| Sonnet 5 | $0.00001 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
self-critique-design-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 12d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Conduct a rigorous two-phase design review with explicit self-critique to reduce confirmation bias. This process forces you to challenge your own assessment, identify blind spots, and produce a validated recommendation with clear confidence levels.
Use this command BEFORE committing to implementation to catch design flaws early.
Variables
DESIGN_DOCUMENT: $1
OUTPUT_DIR: docs/reviews/design-validation/self-critique-design-review/
FILE_NAME: <two-to-three-words-from-DESIGN_DOCUMENT-filename>.md
Instructions
- IMPORTANT: If no
DESIGN_DOCUMENTis provided, stop and ask the user to provide it. - Verify
OUTPUT_DIRexists, create it if it doesn't. - Save output from review to
OUTPUT_DIR/FILE_NAME. - Conduct a two-phase review with explicit self-critique to reduce confirmation bias.
Workflow
Phase 1: Initial Assessment
Analyze the design document and produce:
1.1 Design Strengths (identify exactly 3)
For each strength, document:
- What aspect of the design is strong
- Why it effectively addresses requirements
- Specific evidence or examples supporting this
1.2 Design Concerns (identify exactly 3)
For each concern, document:
- What assumption or decision needs scrutiny
- Why this could be a risk or limitation
- What research or validation would address it
1.3 Integration vs. Build Analysis
Answer these questions explicitly:
- Have we identified existing solutions that solve this or parts of it?
- What specific evidence shows existing solutions won't work?
- What are we planning to build that might already exist?
Phase 2: Self-Critique
Challenge your Phase 1 assessment by working through each category:
2.1 Bias Check
- Am I defending this design because I created it vs. objectively evaluating it?
- What assumptions am I making without evidence?
- Have I researched alternatives thoroughly enough?
- Am I overestimating our ability to build vs. integrate?
2.2 Blind Spots
- What did I miss in the landscape research?
- What edge cases or failure scenarios haven't been considered?
- What stakeholder perspectives aren't represented?
- What technical constraints haven't been validated?
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.
- 12d ago First seen · 220 lines · 7 tokens per session scan A d73ac7b55022
self-critique-design-review is a command published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 1,281 once invoked, about $0.0000 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-30.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.
team-ui
Orchestrate UI/UX design team.