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 skills add KirKruglov/claude-skills-kit --skill release-notes-generatorgit clone --depth 1 https://github.com/KirKruglov/claude-skills-kitWrote 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/kirkruglov/claude-skills-kit/release-notes-generator)<a href="https://agentmods.dev/skills/kirkruglov/claude-skills-kit/release-notes-generator"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/release-notes-generator/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/kirkruglov/claude-skills-kit/release-notes-generator"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/release-notes-generator.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.00105 | $0.02093 |
| Opus 5 | $0.00053 | $0.01046 |
| Sonnet 5 | $0.00021 | $0.00419 |
| Haiku 4.5 | $0.00011 | $0.00209 |
Grade A, and why
release-notes-generator 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 9d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
This skill transforms a plain-language sprint summary or product update file into polished, user-facing release notes for 4 communication channels — without git, CLI, or developer tooling. Designed for non-technical PMs, product owners, and team leads who write sprint results in plain text and need to distribute them across multiple channels.
Input:
- One local file (
.mdor.txt) with sprint results or product update notes - Optional: product name, version / sprint number, audience type (
users|customers|internal)
Output:
- Changelog entry — markdown-formatted, ready to paste into CHANGELOG.md
- Email announcement — subject line + body (2–4 paragraphs)
- In-app / push notification — 1–2 sentences, max 160 characters
- Social post — LinkedIn / X version, conversational tone
Language Detection
Detect the language of the input file:
- If the file content is in Russian: generate all 4 output formats in Russian
- If the file content is in English: generate all 4 formats in English
- If mixed-language content: default to English; add note "Mixed-language input detected — generated in English. Say 'по-русски' to switch."
- If the user's trigger phrase is in Russian but the file is in English: use English for outputs (follow the file)
Instructions
Step 1: Find and Read the Input File
- Look for the file the user mentioned by name
- If no filename given: scan the Cowork workspace for
.mdand.txtfiles; if exactly one such file exists, use it; if multiple exist, list them and ask which one to use
- If no filename given: scan the Cowork workspace for
- Read the file
- Validate:
- If no file found: stop — "No input file found. Please place your sprint summary or product update notes (.md or .txt) in the Cowork workspace and try again."
- If the file is empty or contains fewer than 3 meaningful lines: stop — "The file is too short to generate release notes from. Add at least a few bullet points describing what was released."
- If file is
.docxor.pdf: stop — "release-notes-generator works with .md and .txt files. Please export your document to text format and try again."
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 184 lines · 105 tokens per session scan A 7619d43ec0c7
release-notes-generator is a skill published in the GitHub repository KirKruglov/claude-skills-kit (18 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 2,093 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
release-testing-workflow
Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
app-store-changelog
Generate user-facing App Store release notes from git history since the last tag.
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.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.