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.
npx skills add Yeachan-Heo/oh-my-claudecode --skill loftgit 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/skills/yeachan-heo/oh-my-claudecode/loft)<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-claudecode/loft"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/loft/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/skills/yeachan-heo/oh-my-claudecode/loft"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/loft.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00096 | $0.01214 |
| Opus 5.5 | $0.00038 | $0.00486 |
| Sonnet 5.5 | $0.00019 | $0.00243 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
loft 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loft
Cut no steel until the shape is fair. Shipwrights loft the hull's lines full-scale and fair them before a single plate is cut. Loft applies the same order to design questions: when words have run out — two plausible answers, neither falsifiable by talk — build a cheap runnable artifact, let the captain react to it, and fold that reaction into the decision.
The role contract. The crew builds the artifact; the captain's only job is to react — and that reaction is the decision. The artifact is an instrument for seeing, never a head start on the deliverable.
When to loft
- a design question stalls in prose: repeatedly rephrased, still not settleable ("how should the path page look", "does this state model feel right")
- a navigator map carries a
loftticket - a spec discussion reaches "we would have to see it first"
Do not loft when:
- the question is answerable from repo evidence or by asking the captain (that is interviewing, not lofting)
- the destination itself is unclear (that is fog —
/oh-my-claudecode:ask-navigator) - the answer already lives in an ADR (do not re-loft settled decisions)
- the "design question" is actually a bug (that is the debugger's jurisdiction)
Choose the fork
Pick by what the question is asking. A wrong fork wastes the whole artifact.
Logic fork — is the model right?
For questions about state, business rules, data shape, or algorithms ("does unlocking regress on a retake?", "does this reducer hold at the edges?"):
- Isolate the decision-bearing core — the state machine, reducer, schema, or algorithm — as a pure module: no DOM, no I/O, no framework. Written so that, once the shape is confirmed, it moves into the real codebase unchanged.
- Wrap it in a single clickable HTML shell: one button per scenario, the tricky edge cases walked through in order, full state visible after every click.
- On confirmation the module is ready to lift — it re-enters as real work through launch. During the loft itself
mainstays untouched and the shell stays behind on the branch.
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.
- 1mo ago Changed · +96 tokens per session 60f98c8e1db2
- 1mo ago First seen · 71 lines · 0 tokens per session scan A 4d2bacc4e665
loft is a skill published in the GitHub repository Yeachan-Heo/oh-my-claudecode (40,265 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 1,214 once invoked, about $0.0004 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.
Other skills, from other repositories
dynamic-typography
L2 mechanics for type in motion: variable-font axis animation, kinetic text, per-letter effects, scroll- and pointer-linked type, and typographic state transitions. Fires on implementing or auditing type-specific motion, or when chained from a higher layer. Ownership of motion budgets, timing doctrine, and…
archify-tuning
Improve Archify diagram accuracy, visual quality and complete authoring speed with fewer repairs. Use for generation experiments or evaluating changes to layout, routing, diagnostics, authoring instructions and acceptance rules against actual diagrams and agent traces.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
simplify
Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.
verification-planning
Use before implementing a feature, bug fix, refactor, or cross-system change to plan a credible project-specific verification path.