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.
git 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/commands/florianbruniaux/claude-code-plugins/release-notes)<a href="https://agentmods.dev/commands/florianbruniaux/claude-code-plugins/release-notes"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/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/commands/florianbruniaux/claude-code-plugins/release-notes"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/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.00013 | $0.01818 |
| Opus 5.5 | $0.00005 | $0.00727 |
| Sonnet 5.5 | $0.00003 | $0.00364 |
| Haiku 4.5 | $0.00001 | $0.00182 |
Grade A, and why
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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Generate release notes in 3 formats from git commits for production releases.
Process
- Analyze Git History: Scan commits since last release tag
- Fetch PR Details: Get titles, descriptions via
gh api - Categorize Changes: Group by type (feat, fix, perf, etc.)
- Check Migrations: Detect database migration files
- Generate 3 Outputs: CHANGELOG, PR body, communication message
- Transform Language: Convert tech jargon to product language
Output Formats
1. CHANGELOG.md Section
## [X.Y.Z] - YYYY-MM-DD
### Summary
[1-2 sentence overview of this release]
### New Features
#### [Feature Name] (#PR)
- **Description**: User-facing functionality added
- **Impact**: How it benefits users
### Bug Fixes
- **[Module]**: Description (#issue, tracking-ID)
### Technical Improvements
- [Internal improvements, refactoring, performance]
### Database Migrations
[If applicable - list migration files]
### Statistics
- PRs: X | Features: Y | Fixes: Z | Files changed: N
2. PR Release Body
Uses your project's release template:
.github/PULL_REQUEST_TEMPLATE/release.md.github/pull_request_template_release.md- Or custom location specified in project config
3. Communication Announcement
Generate user-facing announcement (Slack, email, etc.):
- Non-technical language
- Focus on user impact
- Readable formatting (emojis optional)
Template location examples:
.github/COMMUNICATION_TEMPLATE/slack-release.mddocs/templates/release-announcement.md
Migration Alert
If migrations detected:
╔══════════════════════════════════════════════════════════════════╗
║ ⚠️ [ATTENTION] DATABASE MIGRATIONS REQUIRED ║
╠══════════════════════════════════════════════════════════════════╣
║ This release contains X migration(s): ║
║ • 20250110_add_user_preferences ║
║ • 20250112_create_audit_log_table ║
║ Action required: Run migration command after deployment ║
╚══════════════════════════════════════════════════════════════════╝
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 · 246 lines · 13 tokens per session scan A 054d10f4671a
release-notes is a command published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,818 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
changelog
Automatic changelog generation. Produces a structured changelog from commit history.
release
Release notes command. Compiles changes into formats for 3 different audiences.
changelog-gen
CHANGELOG.md update command. Generates a changelog from git history grouped by conventional commit types.
ship
Ship command. Runs the pre-flight gate, decides the version bump, assembles the changelog, and opens the PR via the release-manager agent. Nothing ships unless the gate is green.
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
hotfix
Emergency fix workflow. Manages a fast, safe patching process for production errors.