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 skills/hmbown/codewhale/releasenpx skills add Hmbown/CodeWhale --skill releasegit clone --depth 1 https://github.com/Hmbown/CodeWhaleWhat 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.00000 | $0.00154 |
| Opus 5 | $0.00000 | $0.00077 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
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.
What it actually says
Release
Invocation
Explicit-only for a named version. Loading this skill is not publish authority.
Non-goals
- Do not tag, publish, deploy, or ship packages without separate authorization.
- Do not invent version numbers.
Workflow
- Preflight version consistency and changelog readiness.
- Build/package with locked release commands.
- Smoke test artifacts.
- Produce checksums/notes and a readiness report.
- Stop before any public release action unless explicitly authorized.
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 · 22 lines · 0 tokens per session scan A 7f2b094a2b40
release is a skill published in the GitHub repository Hmbown/CodeWhale (40,889 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 154 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-30.
Other skills, from other repositories
do-release
Cut a new nrflo release. Bumps VERSION, generates human-readable release notes from git log, tags, pushes, monitors the GoReleaser and Docker CI runs, then replaces the GitHub Release body with the synthesized notes. Accepts one SemVer bump argument: patch (+0.0.1), minor (+0.1.0), major (+1.0.0).
herdr-pre-release-audit
Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's pre-release audit, validate docs/next before release, inspect issue refs that release CI will close, or finalize release docs for herdr.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.
helmor-release
Prepare Helmor releases by inspecting the current branch, drafting a concise user-facing Changesets entry first (bump + body — keep it as short as possible), creating any needed pending in-app release announcement under .announcements/, and then showing the user the result with a short menu of adjustments they can…
release-notes
Use when asked to generate release notes, or when the /release-notes command runs — derive user-facing release notes from the change history since the last release.
promoting-dev-to-main
Use when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.