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 drydockgit 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/drydock)<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-claudecode/drydock"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/drydock/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/drydock"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/drydock.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 50 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 136 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 136 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 170 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00084 | $0.04163 |
| Opus 5 | $0.00042 | $0.02082 |
| Sonnet 5 | $0.00017 | $0.00833 |
| Haiku 4.5 | $0.00008 | $0.00416 |
Grade A, and why
drydock 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 5d 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drydock
Lay the keel of the shipyard: one repo, one shared harness, every contributor inherits it. This skill scaffolds the environment that turns "everyone ships" into "everyone ships on the same design language" — it creates the 5 surfaces, seeds them minimally, wires them to the flows that fill them (launch writes CONTEXT/ADR; the launch C5 sediment pass and reviews sediment standards), and reports what exists, what was created, and what stays empty on purpose.
The four pillars and where they physically live:
| Pillar | Surfaces |
|---|---|
| Context (shared background) | CONTEXT.md (glossary) + docs/business/ + docs/adr/ + OMC wiki |
| Rules (boundaries) | CLAUDE.md (thin entry: conventions, principles, index) + docs/standards/ |
| Tools (composable capability) | .omc/skills/ + .mcp.json + scripts/ |
| Standards (the classification society) | design-system/ (tokens, components, patterns) + docs/standards/ |
Metaphor map: the shipyard is the shared facility; the classification society (docs/standards/ + design-system/) sets the rules a ship must pass to be seaworthy; drydock lays the keel; launch ships it.
When to Use
- starting a repo that humans and agents will both build on
- a repo where knowledge lives in people's heads and chat history instead of files
- onboarding: a new teammate or agent should inherit context by reading, not by asking
When Not to Use
- throwaway prototypes with no collaborators
- a repo already running this harness (use
--checkinstead)
Workflow
1. Detect (never clobber)
Inventory what exists before writing anything:
CLAUDE.mdpresent?AGENTS.mdpresent? (rule: if either exists, extend it in place; create the missing one as a one-line pointer to the other; never create both fresh)CONTEXT.md,docs/adr/,docs/standards/,docs/business/,design-system/,.omc/skills/,.mcp.json,scripts/,.gitattributes— which exist, which are missing?- OMC installed? — only worth checking when running inside an OMC session; outside one, skip this check silently (the harness works with or without OMC)
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.
- 5d ago Changed e8d20ed2b25f
- 6d ago Changed bfb4cfb61657
- 9d ago First seen · 338 lines · 84 tokens per session scan A 226b16e37eb6
drydock is a skill published in the GitHub repository Yeachan-Heo/oh-my-claudecode (39,083 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 4,163 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-09-02.
Other skills, from other repositories
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
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…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
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.