Borrowing it
Nothing to install: this file belongs to dixus/claudeframework. 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/dixus/claudeframework/main/.claude/skills/release-notes/SKILL.mdgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote 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/dixus/claudeframework/release-notes)<a href="https://agentmods.dev/skills/dixus/claudeframework/release-notes"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/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/dixus/claudeframework/release-notes"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/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.00043 | $0.01691 |
| Opus 5.5 | $0.00017 | $0.00676 |
| Sonnet 5.5 | $0.00009 | $0.00338 |
| Haiku 4.5 | $0.00004 | $0.00169 |
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aggregate changelog/<branch>.md files into a single quarterly release-notes document for the people who deploy the release. The output is releases/<quarter>.md.
Why this skill exists: The release pipeline rolls out code automatically, but some tickets need manual steps (DB scripts, gateway routes, cache flushes, per-environment config, feature-flag toggles). Each ticket's per-ticket changelog already records these in its ## Manual Steps section (written by /ship Step 5b or /changelog). This skill is the consumer side — it gathers all those sections for one release window into one file the deployer can work through linearly.
Inputs:
<quarter>— required. FormatYYYY-QN, e.g.2026-Q2. Used as the output filename and the title.--since <git-ref>— optional. Override the default "since last release" detection. E.g.--since v2026.04.0or--since 0b6448f.--dry-run— optional. Print the aggregated content to stdout without writing the file.
Throughout, <main> is the repo's default branch (main or master — check git symbolic-ref --short refs/remotes/origin/HEAD).
Step 1 — Determine the changelog set
Decide which changelog/<branch>.md files belong to this release.
- Default (no
--since): find the most recentreleases/*.mdfile (lexicographic max). Read its header — it records the git-ref (**Range:** <ref>..HEAD) where the previous release ended. Use that as the lower bound.- If no prior
releases/*.mdexists, fall back to "all files currently inchangelog/" — first-time bootstrap.
- If no prior
- With
--since <ref>: use<ref>directly. - Build the file list:
- Run
git log <since-ref>..<main> --diff-filter=A --name-only --format= -- changelog/to list changelog files added in the range. Strip duplicates (a file added then renamed shows twice). - Filter: only
changelog/*.md(not subdirectories). - If the resulting list is empty, print "No new changelogs since
<ref>. Nothing to aggregate." and exit.
- Run
Record the upper-bound ref too — git rev-parse HEAD at the time of the run — so the next release knows where this one ended.
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 · 128 lines · 43 tokens per session scan A 5bf90908671b
release-notes is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,691 once invoked, about $0.0002 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-16.
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.