What is comprehensive-design-review?

A command that coordinates five specialized agents to review a design document in parallel and combine their findings into one report.

Checking a design document, collecting the five review parts, and writing a comprehensive validation report.

It brings several validation perspectives together and keeps the results in a single review document.

How basher83/lunar-claude configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/basher83/lunar-claude/main/.claude/commands/design-validation/comprehensive-design-review.md

Clone the repo

git clone --depth 1 https://github.com/basher83/lunar-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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/basher83/lunar-claude/comprehensive-design-review/github.svg)](https://agentmods.dev/commands/basher83/lunar-claude/comprehensive-design-review)

Your own site

<a href="https://agentmods.dev/commands/basher83/lunar-claude/comprehensive-design-review"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/comprehensive-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/basher83/lunar-claude/comprehensive-design-review"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/comprehensive-design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,322 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.01322
Opus 5	$0.00005	$0.00661
Sonnet 5	$0.00002	$0.00264
Haiku 4.5	$0.00001	$0.00132

Measured 11d ago against content hash 99a0d442ced0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

comprehensive-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 11d 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.

.claude/commands/design-validation/comprehensive-design-review.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Execute comprehensive design validation by launching 5 specialized review agents in parallel. Each agent follows its respective command definition. The orchestrator combines all findings into a unified report.

Variables

DESIGN_DOCUMENT: $1 OUTPUT_DIR: docs/reviews/design-validation/comprehensive/ PARTS_DIR: docs/reviews/design-validation/comprehensive/parts/ FILE_NAME: <design-document-slug>-comprehensive-review.md

Instructions

IMPORTANT: If no DESIGN_DOCUMENT is provided, stop and ask the user to provide it.
Verify DESIGN_DOCUMENT exists.
Create OUTPUT_DIR and PARTS_DIR if they don't exist.
Launch ALL 5 subagents in PARALLEL (single message, multiple Task tool calls).
Wait for all to complete.
Read results from PARTS_DIR.
Synthesize into comprehensive report at OUTPUT_DIR/FILE_NAME.

Workflow

Step 1: Launch Parallel Validation Agents

Launch ALL 5 agents in a SINGLE message with multiple Task tool calls:

Agent 1: Self-Critique Review

subagent_type: general-purpose
description: Self-critique design review

Prompt:
Read and follow the command definition at:
.claude/commands/design-validation/self-critique-design-review.md

DESIGN_DOCUMENT: [path from $1]
OUTPUT_DIR: docs/reviews/design-validation/comprehensive/parts/
FILE_NAME: self-critique.md

Execute the command exactly as defined.

Agent 2: Pre-Mortem Analysis

subagent_type: general-purpose
description: Pre-mortem failure analysis

Prompt:
Read and follow the command definition at:
.claude/commands/design-validation/premortem-design-validation.md

DESIGN_DOCUMENT: [path from $1]
OUTPUT_DIR: docs/reviews/design-validation/comprehensive/parts/
FILE_NAME: premortem.md

Execute the command exactly as defined.

Agent 3: Landscape Research

subagent_type: general-purpose
description: Landscape research

Prompt:
Read and follow the command definition at:
.claude/commands/design-validation/landscape-research-protocol.md

DESIGN_DOCUMENT: [path from $1]
OUTPUT_DIR: docs/reviews/design-validation/comprehensive/parts/
FILE_NAME: landscape.md

Extract the problem domain from the design document.
Execute the command exactly as defined.

Read the full file on GitHub · 244 lines

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.

11d ago First seen · 244 lines · 9 tokens per session scan A 99a0d442ced0

Subscribe to this mod's changes

comprehensive-design-review is a command published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 1,322 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.

Design and UX

lunar-claude: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Purpose

Variables

Instructions

Workflow

Step 1: Launch Parallel Validation Agents

What this file has done since we first saw it

Other commands, from other repositories

profile

ui-flow-review

ppt-image2-editable-rebuild

responsive-design-specialist

team-ui

p3-ux-wireframes