Borrowing it
Nothing to install: this file belongs to jayminwest/canopy. 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/jayminwest/canopy/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/jayminwest/canopyWrote 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/jayminwest/canopy/release)<a href="https://agentmods.dev/commands/jayminwest/canopy/release"><img src="https://agentmods.dev/badge/commands/jayminwest/canopy/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/jayminwest/canopy/release"><img src="https://agentmods.dev/badge/commands/jayminwest/canopy/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.00001 | $0.00277 |
| Opus 5.5 | $0.00000 | $0.00111 |
| Sonnet 5.5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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.
This is a copy
86% identical to release — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
body
Analyze all changes since the last release and prepare a new version.
Steps:
- Find the last release tag:
git describe --tags --abbrev=0 2>/dev/null || echo "none" - If there's a previous tag, review changes:
git log <tag>..HEAD --onelineandgit diff <tag>..HEAD - Determine the version bump level. Always use patch unless the user explicitly requests minor or major.
- Bump version in both
package.jsonandsrc/index.tsusingbun run version:bump <level> - Update
CHANGELOG.md— move items from [Unreleased] to the new version section with today's date - Update
CLAUDE.mdif command counts or structure changed - Update
README.md:- Update test count and file count in the Development section (run
bun testto get current numbers) - Update CLI reference tables if commands were added, removed, or had flags changed
- Update command count in Project Structure section if commands were added or removed
- Update any other stats or structural information that changed
- Update test count and file count in the Development section (run
- Commit all changes with a message like "release: vX.Y.Z". Then present a summary of what changed.
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 · 23 lines · 1 tokens per session scan A 3fa8a4875fa0
release is a command published in the GitHub repository jayminwest/canopy (41 stars, last pushed 2mo ago), licensed MIT. It adds 1 tokens to every session and 277 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to release, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.