release-notes

release-notes is a command for Claude Code from Avinava/document-design-system. It costs 20 tokens per session (101 once invoked), scanned A, a copy of estimate, MIT.

A command that writes release notes in Markdown in the user's repository. Release notes summarize changes included in a new version of a product or system.

In plain words
What is it for?
Use it to document the contents of a software release. It can produce HTML or PDF only when those formats are requested.
Why use it?
They give users and teammates a clear record of what changed in a release.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the document-design-system plugin — 6 skills, 36 commands shipped together

Good fit Use it to document the contents of a software release. It can produce HTML or PDF only when those formats are requested.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/avinava/document-design-system/release-notes
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Avinava/document-design-system

Made for: Claude Code.

Or install document-design-system, the plugin that ships this one along with the rest of its 6 skills, 36 commands.

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.

agentmods badge for release-notes

README.md
[![agentmods](https://agentmods.dev/badge/commands/avinava/document-design-system/release-notes/github.svg)](https://agentmods.dev/commands/avinava/document-design-system/release-notes)
Your own site
<a href="https://agentmods.dev/commands/avinava/document-design-system/release-notes"><img src="https://agentmods.dev/badge/commands/avinava/document-design-system/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.

agentmods 80×15 button for release-notes

Your own site · 80×15
<a href="https://agentmods.dev/commands/avinava/document-design-system/release-notes"><img src="https://agentmods.dev/badge/commands/avinava/document-design-system/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 101 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 86% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00101
Opus 5.5 $0.00008 $0.00040
Sonnet 5.5 $0.00004 $0.00020
Haiku 4.5 $0.00002 $0.00010

Measured 26d ago against content hash e18542ddec97, 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 26d 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.

Origin

This is a copy

86% identical to estimate — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/release-notes.md · 12 lines

What it actually says

Use the writing-documents skill. Type slug: release-notes Load references/type-release-notes.md, references/writing.md, and references/evidence.md. Default output is Markdown at the type's conventional path. Load references/output.md and core/ only for requested HTML, PDF, print, designed, or themed output.

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.

  1. 26d ago First seen · 12 lines · 20 tokens per session scan A e18542ddec97

Subscribe to this mod's changes

release-notes is a command published in the GitHub repository Avinava/document-design-system (2 stars, last pushed 10d ago), licensed MIT. It adds 20 tokens to every session and 101 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to estimate, differing in 6 lines, and is treated as a copy.