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 agentmods add skills/haoruilee/oh-my-mcode/shipnpx skills add haoruilee/oh-my-mcode --skill shipgit clone --depth 1 https://github.com/haoruilee/oh-my-mcodeWrote 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/haoruilee/oh-my-mcode/ship)<a href="https://agentmods.dev/skills/haoruilee/oh-my-mcode/ship"><img src="https://agentmods.dev/badge/skills/haoruilee/oh-my-mcode/ship.svg" alt="Measured on agentmods" 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 | $0.00099 | $0.00431 |
| Opus 5 | $0.00049 | $0.00216 |
| Sonnet 5 | $0.00020 | $0.00086 |
| Haiku 4.5 | $0.00010 | $0.00043 |
Grade A, and why
ship 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 4d 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.
What it actually says
Ship
Load agents/release.md. Only if run.json status === accepted. Default is notes + command list. Do not git push unless the user asked for --commit and git is clean enough.
中文名：发布准备。
Inputs
- Accepted
run_id. summary.mdand evidence.
Procedure
showthe run. If status is notaccepted, stop. Do not invent a green verdict.- Prefer
oh-my-mcode ship [run_id]. That writesrelease.mdand prints git/PR commands. - Do not mark Accepted. Verify already did that.
- Host
/teamis unrelated. This is Release on a durable run.
Output contract
- Release notes in the run store.
- Suggested commands. Push only when explicitly requested and the tree is clean enough.
Failure handling
- Rejected / active / cancelled: refuse.
- Dirty unrelated git state: print commands, do not force-push.
Examples
User: ship this run
Write notes and print commands if Accepted.
User: max mode: ship the auth fix
Wrong skill if the work is not yet Accepted. That is max then this skill.
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.
- 4d ago First seen · 51 lines · 99 tokens per session scan A 4d154c7f0eb8
ship is a skill published in the GitHub repository haoruilee/oh-my-mcode (51 stars, last pushed 5d ago), licensed MIT. It adds 99 tokens to every session and 431 once invoked, about $0.0005 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 skills, from other repositories
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
multi-repo-release
Prepares and validates GPT-RAG umbrella releases across component repositories and the AI Landing Zone. Use for manifest pins, changelog entries, release branches, tags, and GitHub Release notes.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".