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 iroha924/mumei --skill releasegit clone --depth 1 https://github.com/iroha924/mumeiWrote 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/iroha924/mumei/release)<a href="https://agentmods.dev/skills/iroha924/mumei/release"><img src="https://agentmods.dev/badge/skills/iroha924/mumei/release.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.1 | $0.00144 | $0.04081 |
| Opus 5 | $0.00072 | $0.02041 |
| Sonnet 5 | $0.00029 | $0.00816 |
| Haiku 4.5 | $0.00014 | $0.00408 |
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 7d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release (mumei release skill)
Releases a new version of the mumei repo. Starts only when the user gives an explicit release instruction (matched via the description; side effects are large, so suppress accidental invocation).
Argument interpretation
| Argument | Meaning |
|---|---|
| (omitted) | patch bump |
patch |
patch bump (0.1.0 → 0.1.1) |
minor |
minor bump (0.1.0 → 0.2.0) |
major |
major bump (0.1.0 → 1.0.0) |
0.2.0 / v0.2.0 |
direct version |
A direct version that matches an existing tag is treated as a retag (re-cut).
No-CHANGELOG policy
mumei does not maintain a CHANGELOG.md. When release notes are needed:
git log v<prev>..v<curr> --oneline
or use the diff auto-generated by the GitHub release UI (Conventional Commits subjects become the release notes as-is). This means:
- less work in the release skill (no CHANGELOG editing step)
- zero risk of "implementation and CHANGELOG drift apart"
- git tags are the single source of truth for version history
The release skill therefore never edits a CHANGELOG. The only version-bump target is .claude-plugin/plugin.json.
Overall flow
main is protected (required status checks, required conversation resolution, linear history, no force push), but enforce_admins: false: the maintainer is a repo admin and can push directly to main. The release flow uses that path — one commit, pushed straight to main, gated by the commit → push → CI watch sequence below. A push to main runs only the codeql job of ci.yml (lint / lint-extra / bats are PR-only), so the task release:check pre-flight gate is the lint/test evidence for the release commit.
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.
- 7d ago First seen · 328 lines · 144 tokens per session scan A d20d4f51e4bb
release is a skill published in the GitHub repository iroha924/mumei (2 stars, last pushed yesterday), licensed MIT. It adds 144 tokens to every session and 4,081 once invoked, about $0.0007 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-31.
Other skills, from other repositories
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
bump-version
A procedure for changing a package and plugin version in several project files at the same time.
task-final-report
Apply the final report and PR publication procedure for a Hyper-Waterfall task. Write the final report (report.md), mark the daily task board complete, create the final commit, push the remote publish/task{N} branch, and create an Open PR to {BASEBRANCH}. Invoke only immediately before PR publication after all stages…
dhpk-deploy-list
A command-line tool that builds a list of files to include in a software deployment from Git history. A deployment is the process of shipping a change to a running environment.
update
Safe cc10x upgrade that preserves local modifications. Stashes diffs, pulls upstream, rebuilds cache, rebases patches. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new versions. Triggers: update cc10x, upgrade cc10x, pull cc10x, sync plugin…
ship
Use when work is verified and ready to leave the machine — branch/PR/merge/deploy/smoke-check. Triggers on "ship it", "deploy", "merge the PR", "push this", "release", "go live", "cutover". Covers git hygiene, PR and merge discipline, deploy-target detection (Cloudflare Workers/Pages via wrangler, Vercel, Convex…