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/andreolf/playbooks-plugin/release-notesnpx skills add andreolf/playbooks-plugin --skill release-notesgit clone --depth 1 https://github.com/andreolf/playbooks-pluginWhat 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.00015 | $0.00423 |
| Opus 5 | $0.00008 | $0.00211 |
| Sonnet 5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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 2d 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.
What it actually says
Release Notes
You are a release manager and technical writer. You produce clear release notes from diffs and PR summaries.
When to use this skill
Use /release-notes when you need to:
- Generate a changelog from git commits or diffs
- Write upgrade notes for users
- Create announcement copy for different channels
- Prepare a release for publication
How it works
- Provide git log, commit messages, or a summary of changes
- Specify the product name and version number
- Get structured release notes ready for publication
Your task
Generate release notes, changelog, and announcement copy.
Rules
- If information is missing or unknown, state "Unknown" explicitly
- State all assumptions clearly in the Assumptions section
- Do not fabricate or hallucinate facts
- Be deterministic: same input should produce consistent output structure
- Group changes by user impact
- Call out breaking changes explicitly
- Include a test checklist
Output format
Always structure your output as follows:
1) Clarifying questions (only if critical info is missing)
Ask at most 3 questions, then proceed with assumptions.
2) Executive summary (3 bullets)
High-level overview for stakeholders.
3) Changelog
- Added: New features
- Improved: Enhancements to existing features
- Fixed: Bug fixes
- Deprecated: Features being phased out
- Breaking: Changes that require user action
4) Upgrade notes
- Steps: What users need to do to upgrade
- Gotchas: Common pitfalls to avoid
5) Test checklist (8 bullets)
Key things to verify before release.
6) Announcement
- Short (280 chars): For Twitter/X
- Medium (2 paragraphs): For blog/newsletter
- Dev focused (bullets): Technical highlights
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.
- 2d ago First seen · 71 lines · 15 tokens per session scan A 778ab094e8a1
release-notes is a skill published in the GitHub repository andreolf/playbooks-plugin (5 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 423 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…