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/jamiepine/voicebox/release-bumpnpx skills add jamiepine/voicebox --skill release-bumpgit clone --depth 1 https://github.com/jamiepine/voiceboxWrote 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/skills/jamiepine/voicebox/release-bump)<a href="https://agentmods.dev/skills/jamiepine/voicebox/release-bump"><img src="https://agentmods.dev/badge/skills/jamiepine/voicebox/release-bump.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.01135 |
| Opus 5 | $0.00027 | $0.00567 |
| Sonnet 5 | $0.00011 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
release-bump 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release-bump — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Bump
Goal
Finalize the changelog draft, bump the version across all tracked files, and create a tagged release commit. After this skill runs, the repo has a clean release commit and tag ready to push.
Prerequisites
ghCLI installed and authenticated (gh auth status).bumpversioninstalled (pip install bumpversionor available in the project venv).- The
[Unreleased]section ofCHANGELOG.mdshould already contain the release narrative. If it's empty or stale, run thedraft-release-notesskill first.
Workflow
-
Verify the working tree is clean (except
CHANGELOG.mdwhich may have the draft).git status --porcelainOnly
CHANGELOG.md(and optionally.agents/files) should be modified. If there are other uncommitted changes, stop and ask the user to commit or stash them first. -
Determine the bump level.
Ask the user if not specified:
patch,minor, ormajor. Check the current version:grep '^current_version' .bumpversion.cfg -
Stamp the changelog.
Read the current
[Unreleased]content fromCHANGELOG.md. Compute the new version (based on bump level and current version). Then:a. Replace the
## [Unreleased]section body with an empty placeholder. b. Insert a new stamped section immediately after## [Unreleased]:## [Unreleased] ## [X.Y.Z] - YYYY-MM-DD <the content that was in [Unreleased]>c. Update the reference links at the bottom of the file:
- Change the
[Unreleased]link to compare against the new tag - Add a new link for the new version
[Unreleased]: https://github.com/jamiepine/voicebox/compare/vX.Y.Z...HEAD [X.Y.Z]: https://github.com/jamiepine/voicebox/compare/vPREVIOUS...vX.Y.Z - Change the
-
Stage the changelog.
git add CHANGELOG.md -
Run bumpversion.
bumpversion --allow-dirty <patch|minor|major>The
--allow-dirtyflag is needed becauseCHANGELOG.mdis already staged. bumpversion will:- Update version strings in all tracked files (see
.bumpversion.cfg) - Create a commit with message
Bump version: X.Y.Z -> A.B.C - Create a tag
vA.B.C
- Update version strings in all tracked files (see
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.
- 4d ago First seen · 125 lines · 54 tokens per session scan A c3043ac10e5e
release-bump is a skill published in the GitHub repository jamiepine/voicebox (52,058 stars, last pushed 25d ago), licensed MIT. It adds 54 tokens to every session and 1,135 once invoked, about $0.0003 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 skills, from other repositories
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
multi-repo-release
Prepares and validates GPT-RAG umbrella releases across component repositories and the AI Landing Zone. Use for manifest pins, changelog entries, release branches, tags, and GitHub Release notes.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.