Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/flz/iaqualink-py/releasegit clone --depth 1 https://github.com/flz/iaqualink-pyWhat 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 | $0.00014 | $0.01304 |
| Opus 5 | $0.00007 | $0.00652 |
| Sonnet 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 3d 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.
- 3d ago First seen · 126 lines · 14 tokens per session scan A 7a8cbed465dc
release is a command published in the GitHub repository flz/iaqualink-py (44 stars, last pushed 7d 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. 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
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.