agentmods.dev

design-review

design-review is a command for Claude Code from EZotoff/ez-omo-config. It costs 12 tokens per session (248 once invoked), scanned A, original, MIT.

A staged review of a proposed design: one agent drafts it, another critiques it, and a third challenges its assumptions. The findings are combined into a revised proposal, while the operator remains responsible for approval.

In plain words
What is it for?
It is for reviewing software designs, product proposals, and other plans that need both constructive feedback and adversarial testing.
Why use it?
It exposes missing requirements, design flaws, and failure cases before implementation begins. Separating the stages makes the review process visible and adjustable.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

not rated 6repo 20d ago A scan 12 tokens original MIT

Good fit It is for reviewing software designs, product proposals, and other plans that need both constructive feedback and adversarial testing.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ezotoff/ez-omo-config/design-review
View source ↗ EZotoff/ez-omo-config
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.

Clone the repo
git clone --depth 1 https://github.com/EZotoff/ez-omo-config

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.

agentmods badge for design-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/ezotoff/ez-omo-config/design-review/github.svg)](https://agentmods.dev/commands/ezotoff/ez-omo-config/design-review)
Your own site
<a href="https://agentmods.dev/commands/ezotoff/ez-omo-config/design-review"><img src="https://agentmods.dev/badge/commands/ezotoff/ez-omo-config/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.

agentmods 80×15 button for design-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/ezotoff/ez-omo-config/design-review"><img src="https://agentmods.dev/badge/commands/ezotoff/ez-omo-config/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 248 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00248
Opus 5.5 $0.00005 $0.00099
Sonnet 5.5 $0.00002 $0.00050
Haiku 4.5 $0.00001 $0.00025

Measured 2mo ago against content hash fd31c560de8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 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.

commands/design-review.md · 16 lines

What it actually says

Run a three-stage specialist design review on the design/proposal at hand. The composition is visible and editable — before spawning, restate the plan below and let the operator adjust stages, ordering, or models if they want; proceed as-adjusted.

Stage 1 — DRAFT: one artistry (or best available creative-generalist) agent produces the design/proposal draft from the brief. Give it full context and freedom on approach.

Stage 2 — CRITIQUE: one oracle agent reviews the draft for soundness: flaws, missing considerations, failure modes. It sees the draft but not stage 1's conversation.

Stage 3 — CHALLENGE: one agent in the mephistopheles category attacks the critiqued draft — adversarial pass on the strongest assumptions. It sees the draft and the critique.

Then synthesize: the final design incorporating what survived, with each material change attributed to which stage forced it, and the open disagreements stated plainly rather than smoothed over.

Boundary: this is analysis, not authorization — the output informs the operator's decision; nothing proceeds anywhere without them saying so.

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. 2mo ago First seen · 16 lines · 12 tokens per session scan A fd31c560de8f

Subscribe to this mod's changes

design-review is a command published in the GitHub repository EZotoff/ez-omo-config (6 stars, last pushed 20d ago), licensed MIT. It adds 12 tokens to every session and 248 once invoked, about $0.0000 per session on Opus 5.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-09-06.

Design and UXPlanningai-codingcoding-assistantdeveloper-productivityoh-my-opencodeopencodeopencode-config
Related

design-review compared with commands from other repositories

design-review next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
design-reviewEZotoff/ez-omo-configCommand620d agoMITA12Claude Code
designjuliusz-cwiakalski/agentic-delivery-osCommand43yesterdayMITA12Claude Code, OpenCode
ccc-themeKevinZai/commanderCommand6yesterdayMITA47Claude Code
extract-foundations-from-screensMozurok/fhorja.devCommand1028d agoMITA83Claude Code
screen-specMozurok/fhorja.devCommand1028d agoMITA88Claude Code
a11ysamibs/skillfoundryCommand121mo agoMITA0Claude Code
/a11y-auditgonzalezpazmonica/saviaCommand49yesterdayMITA75Claude Code