Borrowing it
Nothing to install: this file belongs to AltimateAI/altimate-code. 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/AltimateAI/altimate-code/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/AltimateAI/altimate-codeWrote 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/altimateai/altimate-code/release)<a href="https://agentmods.dev/commands/altimateai/altimate-code/release"><img src="https://agentmods.dev/badge/commands/altimateai/altimate-code/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/altimateai/altimate-code/release"><img src="https://agentmods.dev/badge/commands/altimateai/altimate-code/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.00037 | $0.05490 |
| Opus 5.5 | $0.00015 | $0.02196 |
| Sonnet 5.5 | $0.00007 | $0.01098 |
| Haiku 4.5 | $0.00004 | $0.00549 |
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 — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release altimate-code
Automate the complete release process. The core principle: find and fix everything before tagging. No follow-up PRs.
Input
$ARGUMENTS = version bump type: patch (default), minor, or major. Can also be an explicit version like 0.6.0.
Step 0: Read the Release Guide
Read the official release documentation and current changelog style:
cat docs/RELEASING.md
head -80 CHANGELOG.md
Cross-check RELEASING.md against this skill. If it has new steps or prerequisites, warn the user and adapt.
Step 1: Determine Version
npm info @altimateai/altimate-code version
patchor empty: bump patch (e.g.,0.5.17→0.5.18)minor: bump minor (e.g.,0.5.17→0.6.0)major: bump major (e.g.,0.5.17→1.0.0)- Explicit version (matches
\d+\.\d+\.\d+): use directly
Confirm with user: "Releasing v{NEXT_VERSION} (current: v{CURRENT_VERSION}). Proceed?"
Step 2: Deterministic Preflight
Run the preflight script — it is the gate, not a suggestion:
bun script/release-preflight.ts --version {NEXT_VERSION} --stage pre
It verifies, fail-closed:
- clean worktree (untracked files are only a warning — they must NOT be staged later)
- HEAD equals freshly fetched
origin/main— this is the invariant, not "on branch main". Releasing from a worktree or a branch whose HEAD equalsorigin/mainis fine; push viaHEAD:main. If HEAD diverges, STOP. - no local or remote tag
v{NEXT_VERSION}already exists (stale fork-inherited tags nearly shipped a wrong artifact in v0.9.1) - version is valid SemVer, greater than npm
latest, not already published - every prerelease tag on the target line (
v{X.Y}.*-*) is an ancestor oforigin/main - no open PRs labeled
release-blocker - which previous tag the auto-generated release notes will compare against (sanity-check it: for v0.9.1 the old logic would have diffed against a stray divergent tag and omitted a 165-commit merge)
- marker guard clean
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 · 443 lines · 37 tokens per session scan A 3d2dc29a9d8d
release is a command published in the GitHub repository AltimateAI/altimate-code (813 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 5,490 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
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.
pr
A guided command for preparing a GitHub Pull Request, which is a proposed set of repository changes for review and merging. It reads the branch history and changed files to draft the request.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
create-release-note.en
Generate release notes from PRs and commits.
clean_gone
Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.
ship
Prepare a release branch.