What is release-notes?

A release-notes writing skill for preparing the human-readable part of an Atryum software release announcement.

Use it to draft the matching CHANGELOG.md section for a release, organized by categories such as added, changed, fixed, or security-related work.

It explains changes in terms of user impact, upgrade steps, and security considerations instead of internal code details.

How validmind/atryum configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to validmind/atryum. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/validmind/atryum/main/.claude/skills/release-notes/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/validmind/atryum

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/validmind/atryum/release-notes/github.svg)](https://agentmods.dev/skills/validmind/atryum/release-notes)

Your own site

<a href="https://agentmods.dev/skills/validmind/atryum/release-notes"><img src="https://agentmods.dev/badge/skills/validmind/atryum/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/validmind/atryum/release-notes"><img src="https://agentmods.dev/badge/skills/validmind/atryum/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 732 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00070	$0.00732
Opus 5.5	$0.00028	$0.00293
Sonnet 5.5	$0.00014	$0.00146
Haiku 4.5	$0.00007	$0.00073

Measured 2mo ago against content hash 8a1cf646bd9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/skills/release-notes/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release notes

Why this exists

just release <tag> prepends the CHANGELOG.md section matching the tag to GitHub's auto-generated release notes (--generate-notes supplies the PR list, contributor credits, and compare link; the changelog section supplies the human-readable story). If no matching section exists, the release still goes out with generated notes only — so the changelog is the part that takes judgment, and it's this skill's job.

What good notes look like

The audience is someone operating or upgrading atryum, not someone who watched the commits land. They want to know what changed in behavior, what they must do before or after upgrading, and whether anything is security-relevant. Branch names, internal refactor jargon, and commit shorthand don't communicate that — describe the effect, not the diff.

Follow Keep a Changelog 1.0.0: group entries under Added / Changed / Deprecated / Removed / Fixed / Security, omitting empty groups. The Security section deserves particular care in this project — auth gating, judge hardening, trust boundaries, and anything an operator would want to prioritize an upgrade for belongs there, even if the commit called it a "fix" or "feat".

How to build the section

Find the previous release tag (git tag --sort=-creatordate, ignore backup/scratch tags) and review everything since: git log <prev>..HEAD. PR titles alone hide detail — a single PR here can carry a dozen meaningful commits, so read the commit subjects (and bodies where the subject is vague) before summarizing.
Decide or confirm the version. Semver from the reader's perspective: behavior-visible features → minor, only fixes → patch, breaking config/API/CLI changes → call them out explicitly and bump accordingly.
Update CHANGELOG.md:
- New heading ## [x.y.z] - YYYY-MM-DD (today's date, no v prefix — release-push strips the v from the tag when matching).
- Fold in anything sitting under [Unreleased], leaving that section present but empty.
- Keep the compare links at the bottom of the file in sync.
Sanity-check the release path: just release <tag> builds from a pristine local clone of the tag (at ../atryum-release-<tag>) and reads the notes from the tag's own CHANGELOG.md — so the order is commit the changelog, tag, push the tag, then release. Anything not committed and tagged simply isn't in the release, notes included.

Read the full file on GitHub · 57 lines

Changes

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.

2mo ago First seen · 57 lines · 70 tokens per session scan A 8a1cf646bd9a

Subscribe to this mod's changes

release-notes is a skill published in the GitHub repository validmind/atryum (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 70 tokens to every session and 732 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-30.

Git and workflow Releases Writing and docs

release-notes next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-notesvalidmind/atryum	Skill	11	yesterday	Apache-2.0	A	70	Claude Code
release-announcementpaperclipai/paperclip	Skill	111k	yesterday	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	yesterday	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	8d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	788	yesterday	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	yesterday	Apache-2.0	A	22	Claude Code, Codex

atryum: Skill for Claude Code