Borrowing it
Nothing to install: this file belongs to drhousejunior982-cyber/voicebox.sh. 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/drhousejunior982-cyber/voicebox.sh/main/.agents/skills/draft-release-notes/SKILL.mdgit clone --depth 1 https://github.com/drhousejunior982-cyber/voicebox.shWrote 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/drhousejunior982-cyber/voicebox.sh/draft-release-notes)<a href="https://agentmods.dev/skills/drhousejunior982-cyber/voicebox.sh/draft-release-notes"><img src="https://agentmods.dev/badge/skills/drhousejunior982-cyber/voicebox.sh/draft-release-notes.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.1 | $0.00056 | $0.00833 |
| Opus 5 | $0.00028 | $0.00417 |
| Sonnet 5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
draft-release-notes 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 8d 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.
This is a copy
100% identical to draft-release-notes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Release Notes
Goal
Update the [Unreleased] section at the top of CHANGELOG.md with a narrative release story based on the real changes since the last tag. This is a non-destructive working copy — run it as many times as you want during development.
Workflow
-
Identify the last release tag and gather changes.
LAST_TAG=$(git tag --list "v*" --sort=-v:refname | head -n 1) echo "Last tag: $LAST_TAG"Then collect raw material from three sources:
a. Commit log since last tag:
git log --oneline "$LAST_TAG"..HEADb. GitHub-generated release notes preview (PR titles, new contributors):
gh api repos/:owner/:repo/releases/generate-notes \ -f tag_name="vNEXT" \ -f target_commitish="$(git rev-parse HEAD)" \ -f previous_tag_name="$LAST_TAG" \ --jq '.body'c. Diff stat for theme analysis:
git diff --stat "$LAST_TAG"..HEAD -
Draft the release narrative.
Write markdown for the
[Unreleased]section following the format below. Do not include the## [Unreleased]heading itself — just the body content. -
Update CHANGELOG.md.
Replace everything between
## [Unreleased]and the next## [heading with the new draft. Preserve the HTML comment header and all existing release sections below.The
[Unreleased]section must always exist and always be the first section after the header comments. -
Do NOT commit, tag, or bump versions. Just leave the file modified in the working tree.
Release Story Format
Structure the [Unreleased] section like this:
## [Unreleased]
<One strong opening paragraph: what this release is about and why it matters.
Tie it to concrete shipped changes. No vague hype.>
<One paragraph on major technical shifts, if applicable.>
### <Feature/Theme Group>
- Bullet points with specifics
- Reference PRs where available: ([#123](https://github.com/jamiepine/voicebox/pull/123))
### <Another Group>
- ...
### Bug Fixes
- ...
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.
- 8d ago First seen · 95 lines · 56 tokens per session scan A 98a9f072827f
draft-release-notes is a skill published in the GitHub repository drhousejunior982-cyber/voicebox.sh (5 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 833 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to draft-release-notes, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
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".