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-beta.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-beta)<a href="https://agentmods.dev/commands/altimateai/altimate-code/release-beta"><img src="https://agentmods.dev/badge/commands/altimateai/altimate-code/release-beta/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-beta"><img src="https://agentmods.dev/badge/commands/altimateai/altimate-code/release-beta.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.00065 | $0.02982 |
| Opus 5.5 | $0.00026 | $0.01193 |
| Sonnet 5.5 | $0.00013 | $0.00596 |
| Haiku 4.5 | $0.00006 | $0.00298 |
Grade C, and why
release-beta scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules && bun install --frozen-lockfile How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release altimate-code BETA
Cut a prerelease to the beta npm dist-tag. The whole point: existing
stable (latest) users are never touched. Only people who opted into the
beta channel (npm i -g @altimateai/altimate-code@beta, or a beta install)
receive it. Use this to dogfood a risky release before promoting it to
latest with /release.
Why this is a separate skill (read once)
/releasetags a plainvX.Y.Z→ the workflow publishes tolatest→ every existing user auto-upgrades on next launch. For a big/risky change that is exactly the "brick everyone if there's a bug" risk.- A beta tag has a
-suffix (vX.Y.Z-beta.N)..github/workflows/release.ymlderivesOPENCODE_CHANNELfrom the tag: a-→ thebetachannel →npm publish --tag beta. Thelatestdist-tag is left pointing at the old stable, solatestusers do not move. - The upgrade check (
cli/upgrade.ts) is fail-safe and orders prerelease identifiers, so a beta tester onbeta.1auto-upgrades tobeta.2, and any beta upgrades to the eventual stable. This is verified by the round-trip below.
Input
$ARGUMENTS = the target STABLE version this beta leads to (patch | minor |
major, or an explicit X.Y.Z). Default minor — a big upstream merge is not
a patch. The beta tag becomes vX.Y.Z-beta.N.
Step 1 — Determine the beta version
# current published STABLE (the latest dist-tag)
npm view @altimateai/altimate-code dist-tags --json
- Base stable
X.Y.Zfrom$ARGUMENTS:patch/empty → not typical for a beta; preferminor.minor→ bump minor of the current stable (0.8.10 → 0.9.0).major→ 0.8.10 → 1.0.0.- explicit
X.Y.Z→ use it.
- Find the next
-beta.N: look at the currentbetadist-tag. If it is alreadyX.Y.Z-beta.M, next isbeta.(M+1); otherwise start atbeta.1.
# does a beta for this base already exist?
npm view @altimateai/altimate-code@beta version 2>/dev/null || echo "no beta yet"
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 Changed · +35 lines 8d36c4aeaa26
- 1mo ago First seen · 192 lines · 65 tokens per session scan C a9f45bdaa4ba
release-beta is a command published in the GitHub repository AltimateAI/altimate-code (813 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 2,982 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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.
release
Publish a release branch.