Borrowing it
Nothing to install: this file belongs to flz/iaqualink-py. 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/flz/iaqualink-py/master/.claude/commands/release.mdgit clone --depth 1 https://github.com/flz/iaqualink-pyWrote 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/flz/iaqualink-py/release)<a href="https://agentmods.dev/commands/flz/iaqualink-py/release"><img src="https://agentmods.dev/badge/commands/flz/iaqualink-py/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/flz/iaqualink-py/release"><img src="https://agentmods.dev/badge/commands/flz/iaqualink-py/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.01304 |
| Opus 5.5 | $0.00006 | $0.00522 |
| Sonnet 5.5 | $0.00003 | $0.00261 |
| Haiku 4.5 | $0.00001 | $0.00130 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Command
Create the next versioned git tag. The GitHub Actions release workflow fires automatically on any v* tag push, handling GitHub Release creation and PyPI publishing — including pre-releases, which are published to the real PyPI (not Test PyPI) with pre-release status.
Input
The user may optionally pass rc to create a release candidate instead of a final release.
Steps to Execute
1. Validate Branch and Sync Tags
Run the following commands:
git rev-parse --abbrev-ref HEAD
git fetch --tags
- If HEAD is detached or the branch is not
master, stop and tell the user. Tagging from a non-master branch is almost certainly a mistake. Do not proceed unless the user explicitly confirms they know what they're doing and want to tag this commit anyway. - The
git fetch --tagsensures the local tag list matches the remote before any version analysis — a developer may have pushed a tag that isn't local yet.
2. Determine the Latest Tag
Run:
git tag --sort=-version:refname | head -20
Identify:
- Latest final release tag — highest
vX.Y.Ztag without a pre-release suffix (e.g.v0.6.0) - Latest RC tag for the next version — if any
vX.Y.Z-rc.Ntag exists beyond the latest final release, note the highest N
3. Analyze Commits Since Last Final Release
Run:
git log <latest-final-tag>..HEAD --format="%s%n%b%n---"
This captures both the subject line and the full message body, which is necessary because BREAKING CHANGE: may appear in the commit footer rather than the subject (per the Conventional Commits spec).
Classify across the full output of each commit using these rules:
| Indicator | Bump |
|---|---|
Subject contains ! after the type (e.g. feat!:, fix!:), or any line in the body/footer contains BREAKING CHANGE: |
major |
Subject starts with feat (and no breaking change detected) |
minor |
Only fix, build, chore, ci, docs, refactor, test, perf, style |
patch |
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 · 126 lines · 14 tokens per session scan A 7a8cbed465dc
release is a command published in the GitHub repository flz/iaqualink-py (46 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 14 tokens to every session and 1,304 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
land
Resolve and squash merge one named, currently authorized pull request.
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-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.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
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.
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.