omh-design-orchestration

omh-design-orchestration is a skill for Claude Code, Codex from rlaope/oh-my-hermes. It costs 85 tokens per session (1,561 once invoked), scanned A, original, MIT.

A workflow for coordinating a broad design request across the relevant design, implementation, and review activities.

In plain words
What is it for?
Use it when a project needs design direction, implementation coordination, and a plan for later visual checking.
Why use it?
It turns a vague request to handle design into clear preparation and handoffs, while keeping visual work and verification separate from planning.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it when a project needs design direction, implementation coordination, and a plan for later visual checking.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rlaope/oh-my-hermes/omh-design-orchestration
About the project

oh-my-hermes is an operating layer for Hermes Agent that organizes requests into workflows for planning, research, creation, coding handoffs, operations, and project memory. Hermes users run these workflows through the desktop app, CLI, or messenger app, while the catalogue add-ons extend its native capabilities.

rlaope/oh-my-hermes · 1,677 stars · on GitHub · rlaope.github.io

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.

Any agent
npx skills add rlaope/oh-my-hermes --skill omh-design-orchestration
Clone the repo
git clone --depth 1 https://github.com/rlaope/oh-my-hermes

Made for: Claude Code, Codex.

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 omh-design-orchestration

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-design-orchestration"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-design-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,561 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00085 $0.01561
Opus 5 $0.00043 $0.00781
Sonnet 5 $0.00017 $0.00312
Haiku 4.5 $0.00009 $0.00156

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

Security

Grade A, and why

omh-design-orchestration 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 6d 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.

skills/omh-design-orchestration/SKILL.md · 131 lines

How it starts

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

Design Orchestration

This is a Hermes-native design-orchestration workflow skill.

Why This Exists

design-orchestration lets Hermes users say that they want design handled without making them manually compose four specialist lanes or confusing preparation with completed visual work.

Do Not Use When

  • The request is directly about premium multi-format quality or publishing; use design-quality-gate.
  • The request is directly about frontend implementation, layout, responsive behavior, or a design system; use frontend.
  • The request is directly about WCAG, keyboard, screen-reader, or semantic accessibility; use accessibility-audit.
  • The request is directly about screenshots, visual regression, pixel diff, rendered layout, or a verdict; use visual-qa.

Examples

Good example:

  • Prompt: 디자인 맡겨줘. 기존 프로젝트 맥락을 먼저 보고, 방향과 구현·검증의 다음 단계를 잡아줘.
  • Expected behavior: Prepare design_orchestration/v1 with opaque context references, deliberate direction, existing-lane composition, executor_selection_required, and not_observed visual evidence requirements.
  • Why: The request delegates broad design ownership while leaving implementation and observed QA to the appropriate owners.

Bad example:

  • Prompt: design-orchestration already rendered and visually passed the new page.
  • Expected behavior: Keep rendering and visual PASS not_observed; route the required capture and verdict work to visual-qa.
  • Why: A prepared orchestration contract cannot create implementation or rendered evidence.

Completion Checklist

  • The bounded intent, opaque context references, direction vocabulary, and avoid patterns are explicit.
  • The four downstream lanes retain their direct ownership and the executor is still selection-required.
  • The visual evidence contract keeps visual_verdict not_observed until fresh captures are recorded by the visual-QA owner.

Recovery Notes

  • If only a raw brief exists, let Hermes retain it in chat and create an opaque user-supplied reference instead of storing the brief.
  • If the request narrows to implementation, accessibility, or rendered QA, route to the existing specialist rather than expanding this orchestration surface.

Read the full file on GitHub · 131 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.

  1. 6d ago Changed bae14b4719d3
  2. 9d ago Changed 089f1a206d70
  3. 13d ago First seen · 131 lines · 85 tokens per session scan A e67aadee21e1

Subscribe to this mod's changes

omh-design-orchestration is a skill published in the GitHub repository rlaope/oh-my-hermes (1,677 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 1,561 once invoked, about $0.0004 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.

Related

Other skills, from other repositories