Borrowing it
Nothing to install: this file belongs to lebek/modmixer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lebek/modmixer/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/lebek/modmixerWrote 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/commands/lebek/modmixer/release)<a href="https://agentmods.dev/commands/lebek/modmixer/release"><img src="https://agentmods.dev/badge/commands/lebek/modmixer/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/commands/lebek/modmixer/release"><img src="https://agentmods.dev/badge/commands/lebek/modmixer/release.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.01284 |
| Opus 5.5 | $0.00006 | $0.00514 |
| Sonnet 5.5 | $0.00003 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00128 |
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release
You are running the /release command. Walk through these steps in order. Be concise — one sentence per step at most. Do not narrate plans; just do the work.
1. Find what's new since the last release
Run:
git describe --tags --abbrev=0 2>/dev/nullto get the most recent tag (may be empty if no tags yet).git log <range> --pretty=format:'%h %s%n%b%n---%n'where<range>is<last-tag>..HEADif a tag exists, otherwise justHEAD.
If there are zero commits in the range, stop and tell the user there's nothing to release.
2. Suggest a version bump
Read the current version from package.json (node -p "require('./package.json').version"). Decide a bump level from the commits:
- major — breaking changes, removed features, incompatible config/data formats
- minor — new user-visible features, capabilities, or commands
- patch — bug fixes, internal refactors, doc/test/CI changes only
Tell the user: current version, suggested next version, one short rationale (≤1 sentence). Don't dump the full commit log.
3. Draft release notes
Write user-facing prose grouped by intent in Keep a Changelog style. Only include sections that have content:
## What's new in v<X.Y.Z>
### Added
- ...
### Changed
- ...
### Fixed
- ...
Rules:
- Group by what changed for the user, not by commit subject. Multiple commits often collapse into one bullet.
- Skip noise: lockfile bumps, CI tweaks, internal-only refactors that don't change behavior, formatting/typo commits.
- One short sentence per bullet. No commit hashes. No "by @username".
- If a commit subject already reads as a user-facing change, you can use it largely as-is.
Write the draft to a fresh temp file. Get the path with node -p "require('path').join(require('os').tmpdir(), 'modmixer-release-notes-' + Date.now() + '.md')" (the timestamp avoids collisions with stale files from prior runs that would otherwise trip the Write tool's read-before-write guard) and use that absolute path with the Write tool. Remember the path — you'll pass it to the script in step 5.
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 · 121 lines · 16 tokens per session scan A 6f9bad1d0011
release is a command published in the GitHub repository lebek/modmixer (30 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,284 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-08-30.
Other commands, from other repositories
release-check
Run the complete release readiness pipeline (version checks, changelog, final quality gates) and assign a release confidence score.
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
changelog-review
Review new Claude Code changelog entries since last review and propose Parliament features.
bump-plugin
Bump changed plugin and marketplace version.