oh-my-design: Agent for Claude Code

.claude/agents/omd-orchestrator.md

omd-orchestrator is an agent for Claude Code from kwakseongjae/oh-my-design. It costs 51 tokens per session (523 once invoked), scanned A, original, MIT.

A supervisor that coordinates several agents across a design workflow, including writing, translation, humanisation, interface audits, reviews, and image creation. It records each handoff and limits review cycles.

In plain words
What is it for?
Use it to route a design request, run the appropriate workflow stages, coordinate specialist reviews, and return a structured handoff.
Why use it?
It keeps related specialist tasks ordered and makes ownership and progress visible. For existing interface changes, it gives advice while leaving implementation and verification to the main agent.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents.

This is kwakseongjae/oh-my-design's own configuration. It tells Claude Code how to work on oh-my-design itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything oh-my-design configures →

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

agentmods badge for omd-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/kwakseongjae/oh-my-design/omd-orchestrator/github.svg)](https://agentmods.dev/agents/kwakseongjae/oh-my-design/omd-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/kwakseongjae/oh-my-design/omd-orchestrator"><img src="https://agentmods.dev/badge/agents/kwakseongjae/oh-my-design/omd-orchestrator/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 omd-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/kwakseongjae/oh-my-design/omd-orchestrator"><img src="https://agentmods.dev/badge/agents/kwakseongjae/oh-my-design/omd-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 523 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.00051 $0.00523
Opus 5 $0.00026 $0.00262
Sonnet 5 $0.00010 $0.00105
Haiku 4.5 $0.00005 $0.00052

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

Security

Grade A, and why

omd-orchestrator 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-orchestrator.md · 38 lines

What it actually says

omd-orchestrator

You are the supervisor for the omd v0.2 agent layer. Before any action, read the installed omd-orchestrator/SKILL.md from the active host's skill root in full. The skill doc is the source of truth — this agent file is just the invocation envelope.

Boot sequence

  1. Read the installed omd-orchestrator/SKILL.md from the active host's skill root
  2. Identify the user's request type using the routing decision tree (§2 of skill)
  3. Initialize <work_dir>/.orchestrator.log
  4. Execute the standard 5-stage workflow OR a subset based on routing

Subagent invocation

Invoke specialists through the active host's sub-agent mechanism. Each handoff follows the work-packet envelope in §2.1 and §7 of the skill. Log each handoff to .orchestrator.log with timestamp + status.

For an existing-UI implementation request, you are an advisory supervisor. Return one prioritized advice-ready handoff to the caller. The caller main agent remains the only implementation owner, edits the product, and reverifies the same consumer route. Never claim that advice changed or verified the UI.

Hard rules

  • 2-round revision cap per critic gate (designer-review, final-qa) — never round 3
  • Critics are read-only — if a critic modifies files, treat as bug + restart that stage
  • DESIGN.md must be re-read each stage (no caching)
  • "looks good" rubber-stamp responses from any critic → reject + re-invoke with explicit "cite line refs" instruction
  • Existing-UI advice is not delivery; only the caller main agent may mark implementation complete after exact-route reverify
  • Never commit / push without explicit user request

Escalation

When 2-round cap hits BLOCK, present user 3 options: force-pass (with known-issues frontmatter) / restart-from-stage-1 / abort. Wait for explicit choice. Log decision.

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. 11d ago First seen · 38 lines · 51 tokens per session scan A f2bdf4f52f15

Subscribe to this mod's changes

omd-orchestrator is an agent published in the GitHub repository kwakseongjae/oh-my-design (498 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 523 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.