Borrowing it
Nothing to install: this file belongs to lttr/claude-marketplace. 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/lttr/claude-marketplace/master/.claude/commands/release.mdgit clone --depth 1 https://github.com/lttr/claude-marketplaceWrote 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/lttr/claude-marketplace/release)<a href="https://agentmods.dev/commands/lttr/claude-marketplace/release"><img src="https://agentmods.dev/badge/commands/lttr/claude-marketplace/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/lttr/claude-marketplace/release"><img src="https://agentmods.dev/badge/commands/lttr/claude-marketplace/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.00014 | $0.00291 |
| Opus 5 | $0.00007 | $0.00146 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
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 8d 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
Release Command
Automate the plugin release workflow:
- Check for uncommitted changes. If any exist, stop and tell the user to commit them first. Forgotten work needs its own feat or fix commit and must never be lumped into the version bump.
- Detect which plugin changed. Look at the git log for files changed since the last commit that touched version files, and determine which plugin directory those changes belong to.
- Bump the version in both
plugins/<plugin-name>/.claude-plugin/plugin.jsonand the matching entry in.claude-plugin/marketplace.json. - Update README.md: sync plugin descriptions, version numbers, and feature lists with the current state.
- Commit the version bump with a conventional commit message.
- Push to remote.
Version Bump Rules
- Minor (0.x.0) for new features, commands, or refactoring. This is the default.
- Patch (0.0.x) when the commits are only fixes or docs.
- Major (x.0.0) for breaking changes: ask the user to confirm first.
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.
- 8d ago First seen · 22 lines · 14 tokens per session scan A ac16d8570535
release is a command published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 291 once invoked, about $0.0001 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 commands, from other repositories
create-release-note
Generate comprehensive release documentation from recent commits, producing two distinct outputs: a customer-facing release note and a technical engineering note.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.
wrap
The session-scoped landing step after ship: flips board rows, merges the operator's own green PRs one at a time, checks deploys, tidies branches and worktrees, writes the activity line, calls /kit:retro when a shipped PR merged, and prints the skim-first report. Use when the operator says to wrap up or close out the…
versioning
Universal version file discovery and sync. Works with any project structure.