Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sembraniteam/claude-plugins/plugin install changelog-managerWrote 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/sembraniteam/claude-plugins/generate-release-notes)<a href="https://agentmods.dev/skills/sembraniteam/claude-plugins/generate-release-notes"><img src="https://agentmods.dev/badge/skills/sembraniteam/claude-plugins/generate-release-notes/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/skills/sembraniteam/claude-plugins/generate-release-notes"><img src="https://agentmods.dev/badge/skills/sembraniteam/claude-plugins/generate-release-notes.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.00085 | $0.01528 |
| Opus 5.5 | $0.00034 | $0.00611 |
| Sonnet 5.5 | $0.00017 | $0.00306 |
| Haiku 4.5 | $0.00009 | $0.00153 |
Grade A, and why
generate-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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Release Notes
Generate platform-specific, bilingual release notes from the latest entry in CHANGELOG.md using generate-release-notes.py. Produces separate output files per platform with enforced character limits and user-friendly language.
Prerequisites
CHANGELOG.mdmust exist with at least one version entry — invokegenerate-changelogfirst if needed- Python 3 (standard library only, no pip install)
- Settings at
.claude/changelog-manager.local.md— invokechangelog-configif missing
Platform Reference
| Platform | Output File | Char Limit | Tone |
|---|---|---|---|
playstore |
RELEASE_NOTES_PLAYSTORE |
500 per language | Concise, bullet-first |
appstore |
RELEASE_NOTES_APPSTORE |
4,000 per language | Friendly, feature-rich |
web |
RELEASE_NOTES |
No limit | Detailed, full context |
Context & Inputs
Read settings — read .claude/changelog-manager.local.md. If it does not exist, use defaults and notify the user:
languages:
- code: en_US
name: English
platforms:
- web
Read CHANGELOG.md — extract the latest version block (first ## [vX.Y.Z] section):
- Version number and release date
- All categorized entries by section (Breaking Changes, Added, Changed, Fixed, Reverted)
This is the only place items come from — the script itself does not read CHANGELOG.md or extract anything from it. Deciding which entries become --item flags (if any) is entirely up to Claude, done here.
Generate Notes
For each platform, build and run one command with all language blocks:
python3 $CLAUDE_PLUGIN_ROOT/scripts/generate-release-notes.py \
--platform <platform> \
--lang <code1> --summary "<summary1>" [--item "<item1>" --item "<item2>"] [--outro "<outro1>"] \
--lang <code2> --summary "<summary2>" [--item "<item1>" --item "<item2>"] [--outro "<outro2>"]
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 101 lines · 85 tokens per session scan A bece1abb3c05
generate-release-notes is a skill published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 1,528 once invoked, about $0.0003 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-31.
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.
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.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.