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-notesnpx skills add FlorianBruniaux/claude-code-plugins --skill release-notesgit 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)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/release-notes"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/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 | $0.00013 | $0.01847 |
| Opus 5 | $0.00006 | $0.00924 |
| Sonnet 5 | $0.00003 | $0.00369 |
| Haiku 4.5 | $0.00001 | $0.00185 |
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 yesterday.
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 — 249 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.
- yesterday First seen · 249 lines · 13 tokens per session scan A e456cbc56fc9
release-notes is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 1,847 once invoked, about $0.0001 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
release
Cut a FastMCP release end to end. Use when the maintainer says "cut a release", "prep a patch", "ship 4.x.y", or asks what a release would contain. Covers the notes preview, the title pun, the docs changelog PR that must land before the tag, the tag itself, the publish fan-out, and verifying gofastmcp.com actually…
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
update-project-version
Update the NeMo Relay project version across Cargo, Node, and lockfiles without leaving release surfaces out of sync.
ship
Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'.…
harn-release
Use for Harn release prep, version bumps, publishing, tags, and release notes.