Borrowing it
Nothing to install: this file belongs to rudraptpsingh/axon. 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/rudraptpsingh/axon/master/.claude/commands/release-check.mdgit clone --depth 1 https://github.com/rudraptpsingh/axonWrote 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/rudraptpsingh/axon/release-check)<a href="https://agentmods.dev/commands/rudraptpsingh/axon/release-check"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/release-check/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/rudraptpsingh/axon/release-check"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/release-check.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.00000 | $0.00160 |
| Opus 5.5 | $0.00000 | $0.00064 |
| Sonnet 5.5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
release-check 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 2mo 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
Pre-release validation checklist. Run all steps in order, stop at first failure.
cargo build --release— must compile cleanlycargo test --workspace— all tests passpython3 scripts/eval_cpu_stress.py ./target/release/axon— all checks passpython3 scripts/mcp_exercise_all_tools.py ./target/release/axon— all 7 tools respond with ok=truebash scripts/e2e-real-scenario.sh— all steps pass- Verify
axon --versionmatches version in crates/axon-cli/Cargo.toml
Report: [ok] or [FAIL] for each step. If all pass, say "[ok] Ready to release."
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.
- 2mo ago First seen · 11 lines · 0 tokens per session scan A 0fcc16558375
release-check is a command published in the GitHub repository rudraptpsingh/axon (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 160 tokens. 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
ng-ship-review
Portable command prompt generated from skills/checking-release-readiness/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
wg-release
Manage versions and generate changelogs for the wicked-garden plugin.
queue
"What's coming up — plan steps, releases, backlog, and overdue decisions?".
ship
Deliver completed work with validation and documentation.
release-train
Autonomous multi-PR release train — plan stacked single-concern PRs, open each on its own branch, monitor CI, rebase on conflicts, and ship in dependency order while you sleep. Driven by report.html horizon item 'Autonomous Multi-PR Release Trains'.
land
Resolve and squash merge one named, currently authorized pull request.