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 ao92265/claude-code-playbook --skill changeloggit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/changelog)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/changelog"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/changelog/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/ao92265/claude-code-playbook/changelog"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/changelog.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.00082 | $0.00603 |
| Opus 5 | $0.00041 | $0.00302 |
| Sonnet 5 | $0.00016 | $0.00121 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
changelog 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.
What it actually says
Changelog Generation
Generate a formatted changelog entry from recent git commits.
Steps
-
Determine the range:
- Find the last tag:
git describe --tags --abbrev=0 2>/dev/null - If no tags exist, use the last 20 commits
- Ask the user if they want a different range
- Find the last tag:
-
Collect commits:
git log <last-tag>..HEAD --oneline --no-merges- If using conventional commits, parse prefixes (feat:, fix:, docs:, chore:, etc.)
- If not using conventional commits, categorize by analyzing the commit message content
-
Categorize changes:
- Added — new features (feat:, add, new, introduce)
- Changed — modifications to existing functionality (update, modify, refactor, improve)
- Fixed — bug fixes (fix:, resolve, correct, patch)
- Removed — removed features or deprecated code (remove, delete, drop, deprecate)
- Security — security-related changes (security, vulnerability, CVE)
- Breaking Changes — anything that breaks backward compatibility (BREAKING, breaking:)
-
Format the entry:
- Use Keep a Changelog format
- Date in ISO format (YYYY-MM-DD)
- Group by category with bullet points
- Include PR/issue references if present in commit messages
-
Write to CHANGELOG.md:
- If file exists, insert new entry at the top (after the header)
- If file doesn't exist, create it with the standard header
- Preserve all existing entries — never modify past entries
-
Show the user for review:
- Display the new entry
- Wait for confirmation before committing
Important
- Never modify existing changelog entries — only add new ones at the top.
- Preserve the user's commit style — if they don't use conventional commits, don't force it.
- Include attribution — if commits reference PRs or contributors, include them.
- Ask before committing — the changelog is the user's release narrative.
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 · 62 lines · 82 tokens per session scan A ddb24608bda6
changelog is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 603 once invoked, about $0.0004 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
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.