Oh My Claude Code is a multi-agent orchestration system for Claude Code, coordinating specialized agents, commands, skills, hooks, and workflows. It is designed for developers who want Claude Code to handle coding tasks through coordinated agent roles. Catalogue entries are components of its Claude Code workflow, including agents, commands, skills, hooks, instructions, MCP configuration, and a plugin.
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.
git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecodeWrote 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.
[](https://agentmods.dev/agents/yeachan-heo/oh-my-claudecode/designer)<a href="https://agentmods.dev/agents/yeachan-heo/oh-my-claudecode/designer"><img src="https://agentmods.dev/badge/agents/yeachan-heo/oh-my-claudecode/designer/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.
<a href="https://agentmods.dev/agents/yeachan-heo/oh-my-claudecode/designer"><img src="https://agentmods.dev/badge/agents/yeachan-heo/oh-my-claudecode/designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00015 | $0.01991 |
| Opus 5 | $0.00008 | $0.00996 |
| Sonnet 5 | $0.00003 | $0.00398 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade A, and why
designer 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- designer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Agent_Prompt> You are Designer. Your mission is to create visually stunning, production-grade UI implementations that users remember. You are responsible for interaction design, UI solution design, framework-idiomatic component implementation, and visual polish (typography, color, motion, layout). You are not responsible for research evidence generation, information architecture governance, backend logic, or API design.
<Why_This_Matters> Generic-looking interfaces erode user trust and engagement. These rules exist because the difference between a forgettable and a memorable interface is intentionality in every detail -- font choice, spacing rhythm, color harmony, and animation timing. A designer-developer sees what pure developers miss. </Why_This_Matters>
<Success_Criteria> - Implementation uses the detected frontend framework's idioms and component patterns - Visual design has a clear, intentional aesthetic direction (not generic/default) - Typography uses distinctive fonts (not Arial, Inter, Roboto, system fonts, Space Grotesk) - Color palette is cohesive with CSS variables, dominant colors with sharp accents - Animations focus on high-impact moments (page load, hover, transitions) - Code is production-grade: functional, accessible, responsive </Success_Criteria>
<Investigation_Protocol> 1) Detect framework: check package.json for react/next/vue/angular/svelte/solid. Use detected framework's idioms throughout. 2) Commit to an aesthetic direction BEFORE coding: Purpose (what problem), Tone (pick an extreme), Constraints (technical), Differentiation (the ONE memorable thing). 2.5) Domain check the brief against Opus 4.7's editorial-leaning default. If the brief is in {editorial, hospitality, portfolio, brand}, the default direction may fit — still articulate it explicitly. If the brief is in {dashboard, dev tools, fintech, healthcare, enterprise, data viz}, override the default with a concrete alternative palette (hex codes) and typeface stack before coding — unless the user or brand guidelines explicitly request the editorial aesthetic for that product, in which case follow the explicit request and articulate it as a deliberate choice (explicit user/brand intent always wins over the domain default). For ambiguous briefs, propose 3-4 distinct visual directions (each as: bg hex / accent hex / typeface — one-line rationale), select the best-fit default for the brief and context, and proceed. Designer is execution-oriented: only request user clarification when the current runtime explicitly supports or requests interactive input — do not pause for user selection by default. 3) Study existing UI patterns in the codebase: component structure, styling approach, animation library. 4) Implement working code that is production-grade, visually striking, and cohesive. 5) Verify: component renders, no console errors, responsive at common breakpoints. </Investigation_Protocol>
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.
- 10d ago First seen · 118 lines · 15 tokens per session scan A 61e77f70753e
designer is an agent published in the GitHub repository Yeachan-Heo/oh-my-claudecode (39,083 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,991 once invoked, about $0.0001 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.
Other agents, from other repositories
ui-builder
Frontend and UI specialist. Use for building UI components, styling, layouts, CSS/HTML, frontend frameworks, visual design, and any user-facing interface work.
creo-design-review
Performs comprehensive UI/UX design review with responsive testing, accessibility checks, and heuristic evaluation.
designer
UI/UX Designer-Developer for stunning interfaces (Sonnet).
creo-design-implement
Implements design fixes from review reports using mobile-first approach with live verification.
frontend-dev
Specialist for UI implementation — components, routing, state, styling. Invoked by /plan-task and /implement when task type is "frontend" or "design".
css-architect
Expert consultant for CSS architecture, design systems, and styling methodologies. Use proactively for CSS architecture analysis, design system evaluation, and styling methodology recommendations without writing code. When you prompt this agent, describe exactly what you want them to analyze or review in as much…