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/florianbruniaux/claude-code-plugins/release-notes-generatornpx skills add FlorianBruniaux/claude-code-plugins --skill release-notes-generatorgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/release-notes-generator)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/release-notes-generator"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/release-notes-generator.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.00059 | $0.01572 |
| Opus 5 | $0.00030 | $0.00786 |
| Sonnet 5 | $0.00012 | $0.00314 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade A, and why
release-notes-generator 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 today.
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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Generate comprehensive release notes in 3 formats from git commits.
Workflow
- Analyze git history since last release tag or specified version
- Fetch PR details (titles, descriptions, labels) via
gh api - Categorize changes into features, bug fixes, improvements, security, breaking changes
- Generate 3 outputs: CHANGELOG.md section (technical), PR release body (semi-technical), Slack message (user-friendly)
- Transform language from technical jargon to accessible messaging
- Alert on migrations if database migrations are detected
How to Use
Basic Usage
Generate release notes since last release
Create release notes for version 0.18.0
With Specific Range
Generate release notes from v0.17.0 to HEAD
Preview Only
Preview release notes without writing files
Output Formats
1. CHANGELOG.md Section
Technical format for developers:
## [0.18.0] - 2025-12-08
### Objective
[1-2 sentence summary]
### New Features
#### [Feature Name] (#PR)
- **Description**: ...
- **Impact**: ...
### Bug Fixes
- **[Module]**: Description (#issue, [error-tracker] ISSUE-XX)
### Technical Improvements
#### Performance / UI/UX / Architecture
- [Description]
### Database Migrations
[If applicable]
### Statistics
- PRs: X
- Features: Y
- Bugs: Z
2. PR Release Body
Uses template from .github/PULL_REQUEST_TEMPLATE/release.md:
- Objective summary
- Features with specs links
- Bug fixes with error tracker references
- Improvements by category
- Migration instructions
- Deployment checklist
3. Slack Announcement
Product-focused format from .github/COMMUNICATION_TEMPLATE/slack-release.md:
- PR link included for traceability
- Non-technical language
- Focus on user impact (end-users, admins, stakeholders)
- Emojis for readability
- Statistics summary
Workflow Integration
This skill integrates with the release workflow:
1. Analyze commits: git log <last-tag>..HEAD
2. Determine version number (MAJOR.MINOR.PATCH)
3. Generate 3 outputs
4. Create PR develop -> main with "Release" label
5. Update CHANGELOG.md
6. After merge: create git tag
7. Generate Slack announcement
What ships with it
7 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.
- today First seen · 251 lines · 59 tokens per session scan A c5a968fe89fa
release-notes-generator is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 1,572 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-09-04.
Other skills, from other repositories
create-manifest
Create a Trellis migration manifest and matching docs-site changelogs for a target release by analyzing commits since the previous release. Use when preparing a patch, beta, rc, or minor release manifest.
release
Release a new version of the mumei repository. Invoke when the user gives an explicit release instruction ("release it", "/release", "patch release", "ship 0.2.0"). Takes no argument or "patch" / "minor" / "major" for a SemVer bump, or a direct version such as "0.2.0". Wraps any uncommitted changes into a single…
lfe-archivist
Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.
sprint-close
Merge sprint branch to base branch, tag release, and clean up branches.
release
Create a GitHub release with auto-generated changelog. Triggers: "release", "/release", "create release", "сделай релиз".
marketing-release-handoff
KIOKU の release (v0.X.Y tag publish) 後に、PM → マーケ担当への引き継ぎ資料を tools/claude-brain/marketing/handoff/YYMMDDNNv{VERSION}-release-summary.md (NN = 同日 N 件目の連番) として自動生成する。Changelog + release PRs から user-facing 変化だけを抽出し、バグ fix / 内部 refactor / LEARN 組織知は除外。記事ネタ候補 3 本 + 想定読者 + 既存 article 資産 pointer 付き。/marketing-release-handoff…