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 releasegit 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/release)<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-claudecode/release"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/release/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/release"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00027 | $0.01947 |
| Opus 5.5 | $0.00011 | $0.00779 |
| Sonnet 5.5 | $0.00005 | $0.00389 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
release 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
A thin, repo-aware release assistant. On first run it inspects the project and CI to derive release rules, stores them in .omc/RELEASE_RULE.md for future use, then walks you through a release using those rules.
Usage
/oh-my-claudecode:release [version]
versionis optional. If omitted the skill will ask. Acceptspatch,minor,major, or an explicit semver like2.4.0.- Add
--refreshto force re-analysis of the repo even when a cached rule file exists.
Execution Flow
Step 0 — Load or Build Release Rules
Check whether .omc/RELEASE_RULE.md exists.
If it does NOT exist (or --refresh was passed): Run the full repo analysis below and write the file.
If it DOES exist: Read the file. Then do a quick delta check — scan .github/workflows/ (or equivalent CI dirs: .circleci/, .travis.yml, Jenkinsfile, bitbucket-pipelines.yml, gitlab-ci.yml) for any modifications newer than the last-analyzed timestamp in the rule file. If relevant workflow files changed, re-run the analysis for those sections and update the file. Report what changed.
Step 1 — Repo Analysis (first run or --refresh)
Inspect the repo and answer the following. Write answers into .omc/RELEASE_RULE.md.
1a. Version Sources
- Locate all files that contain a version string matching the current version in
package.json/pyproject.toml/Cargo.toml/build.gradle/VERSIONfile / etc. - List each file and the field or regex pattern used to find the version.
- Detect whether there is a release automation script (e.g.
scripts/release.*,Makefile releasetarget,bump2version,release-it,semantic-release,changesets,goreleaser).
1b. Registry / Distribution
- npm (
package.jsonwithpublishConfigornpm publishin CI), PyPI (pyproject.toml+twine/flit), Cargo (Cargo.toml), Docker (Dockerfile+ push step), GitHub Packages, other. - Is there a CI step that publishes automatically on tag push? Which workflow file and job?
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 First seen · 199 lines · 27 tokens per session scan A 6042cc1c8ee0
release is a skill published in the GitHub repository Yeachan-Heo/oh-my-claudecode (40,237 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,947 once invoked, about $0.0001 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-03.
Other skills, from other repositories
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers the Changelog line from each PR merged since the last stable tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
project-release
Cut a release of this project (maven-decoder-mcp): draft notes, verify the gate, tag, push, watch CI, and confirm packages on PyPI, npm, Docker Hub, and GitHub. Use when the user says "release", "cut a release", "ship it", "tag a version", or asks about the release process, release notes, or publishing.
deploy-automation
Workflows and best practices for CI/CD automation, deployment strategies, and production releases. Use when implementing or improving deployment pipelines, managing environments, or planning production releases.
tendril-release
Updates the used Ivy NuGet packages to the latest stable versions in a branch from development, builds/verifies, merges into development, creates a PR into main, merges it, merges main back to development, and triggers the GitHub Actions release workflow.
merge
The ship gate — the only skill that pushes a feature branch, opens its PR and merges. --staging checks that pre-merge passed on the branch tip, pushes, opens the feature→staging PR, waits for green CI, merges, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships…