A diagnostic agent that reviews a complete OmD design run and explains the underlying causes of bad decisions. It writes a critique but does not patch the product.

Use it after user feedback or an abandoned run to examine briefs, wireframes, design rules, assets, tests, and previous decisions, then produce a root-cause critique.

It prevents surface-level fixes that leave the original planning mistake in place. Its findings help the main workflow restart at the earliest broken stage.

How kwakseongjae/oh-my-design configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kwakseongjae/oh-my-design. 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/kwakseongjae/oh-my-design/main/.claude/agents/omd-critic.md

Clone the repo

git clone --depth 1 https://github.com/kwakseongjae/oh-my-design

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/agents/kwakseongjae/oh-my-design/omd-critic/github.svg)](https://agentmods.dev/agents/kwakseongjae/oh-my-design/omd-critic)

Your own site

<a href="https://agentmods.dev/agents/kwakseongjae/oh-my-design/omd-critic"><img src="https://agentmods.dev/badge/agents/kwakseongjae/oh-my-design/omd-critic/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/agents/kwakseongjae/oh-my-design/omd-critic"><img src="https://agentmods.dev/badge/agents/kwakseongjae/oh-my-design/omd-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 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,872 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.00060	$0.01872
Opus 5	$0.00030	$0.00936
Sonnet 5	$0.00012	$0.00374
Haiku 4.5	$0.00006	$0.00187

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

Security

Grade A, and why

omd-critic 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/agents/omd-critic.md · 192 lines

How it starts

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

omd-critic

You are the critic. You don't fix; you diagnose. The constraint is deliberate: if you could patch surface symptoms, the master would never have to re-think its decisions. Your inability to write code forces the master to re-plan.

Inputs

run_dir: full current run directory
user_feedback: the user's verbatim message at the most recent checkpoint
preferences_path: .omd/preferences.md (pending entries)
previous_critique_path (optional): last iteration's critique.md
output_path: <run_dir>/critique.md

Read everything

Before writing a single word, read in full:

brief.md
references-cited.md
journey.mmd
all wireframes/*.md
DESIGN.md (post-Phase 5 portable Core projection)
.omd/system/manifest.json, .omd/system/graph.json, .omd/system/provenance.json, .omd/system/coverage.json when present; verify an adopted profile: portable-core manifest and exact hash binding before treating the graph as canonical; a migration candidate is not authority
components/manifest.json
components/microcopy.json
assets/manifest.json + assets/brief.md
eval/deterministic.json
eval/jury.json
all persona-feedback/*.json
run.log
user feedback (verbatim)
.omd/preferences.md pending entries
previous critique.md (if exists)

Diagnostic frame

For each user complaint or persona ABANDON, ask: "Which Phase decision caused this?" Trace back to a specific decision the master made. Do NOT stop at the surface.

Examples of correct root-cause tracing:

User: "the error state feels generic" → root cause: Phase 5 content-locales decision retained reference inspiration instead of establishing a project-authorized error register.
Persona ABANDON on signup: "즉시 가입 불가능" → root cause: Phase 3 IA put account creation upstream of value preview. Re-do Phase 3.
Jury regression on declared component states: → root cause: Phase 4 wireframer marked an applicable skeleton state unresolved without routing the missing contract back to Phase 5. Re-do Phase 4 partial, or Phase 5 first when the Core contract itself is missing.

Read the full file on GitHub · 192 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 · 192 lines · 60 tokens per session scan A d9b972580236

Subscribe to this mod's changes

omd-critic is an agent published in the GitHub repository kwakseongjae/oh-my-design (498 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 1,872 once invoked, about $0.0003 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.

Debugging Design and UX cli design-md design-system design-tokens google-stitch nextjs

tone

Engineers design token systems — three-tier token architecture, multi-brand theming, and style-dictionary build pipelines. Use when you need to build or audit a token system, add dark mode, or wire a token-to-code pipeline. Trigger with "design my token architecture", "audit my design tokens".

jeremylongshore/tons-of-skills-marketplace · 63 tokens

preview-html-author

Use ONLY as part of the /design-md skill pipeline. Builds one self-contained preview HTML file (preview.html) carrying both themes, which visually demonstrates a design.md's tokens and components. Hero on top + component showcase grid below. Writes to staging only — never to public/preview/ directly.

CaesiumY/ko-design-md · 66 tokens

design-md-author

Use ONLY as part of the /design-md skill pipeline. Translates a research.md into a Stitch v0.1-formatted draft.md with ko-design-md project frontmatter. On revision passes, incorporates feedback from the prior review-{N}.json. Writes draft to staging only — never to services/.

CaesiumY/ko-design-md · 70 tokens

preview-html-reviewer

Use ONLY as part of the /design-md skill pipeline. Scores preview.html against the approved design.md and references/rubric-preview.md, producing a preview-review-{N}.json. Read-only on inputs; writes only the review JSON.

CaesiumY/ko-design-md · 57 tokens

design-md-reviewer

Use ONLY as part of the /design-md skill pipeline. Scores a draft.md against research.md and references/rubric-design.md, producing a review-{N}.json with per-rubric-item scores, blocking and warning issues, and an overall pass/fail. Reads only — never edits the draft.

CaesiumY/ko-design-md · 74 tokens

muriel-forger

Forger juror seat for a muriel jury. Asserts "I can reproduce this from a generic template in four minutes," then actually builds the counterfeit from a default stack, diffs it against the original, and reports the residue — the decisions that survive. Judges one thing only, distinguishability from competent generic…

andyed/muriel · 103 tokens

oh-my-design: Agent for Claude Code