agentmods.dev

changelog

changelog is a skill for Claude Code from ao92265/claude-code-playbook. It costs 82 tokens per session (603 once invoked), scanned A, original, MIT.

A tool for turning recent Git commits into a Keep a Changelog-style release summary, grouped by the kind of change.

In plain words
What is it for?
Use it to summarize commits since the latest tag, or the last 20 commits when no tag exists, into categorized changelog sections.
Why use it?
It saves time when preparing release notes and makes features, fixes, removals, security changes, and breaking changes easier to scan.

Skill for Claude Code

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

Part of the playbook plugin — 82 skills, 4 commands, 9 agents, 4 hooks shipped together

not rated 13repo today A scan 82 tokens original MIT

Good fit Use it to summarize commits since the latest tag, or the last 20 commits when no tag exists, into categorized changelog sections.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ao92265/claude-code-playbook/changelog
View source ↗ ao92265/claude-code-playbook
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.

Any agent
npx skills add ao92265/claude-code-playbook --skill changelog
Clone the repo
git clone --depth 1 https://github.com/ao92265/claude-code-playbook

Made for: Claude Code.

Or install playbook, the plugin that ships this one along with the rest of its 82 skills, 4 commands, 9 agents, 4 hooks.

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 changelog

README.md
[![agentmods](https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/changelog/github.svg)](https://agentmods.dev/skills/ao92265/claude-code-playbook/changelog)
Your own site
<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.

agentmods 80×15 button for changelog

Your own site · 80×15
<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>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 603 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.00603
Opus 5.5 $0.00033 $0.00241
Sonnet 5.5 $0.00016 $0.00121
Haiku 4.5 $0.00008 $0.00060

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

Security

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

skills/changelog/SKILL.md · 62 lines

What it actually says

Changelog Generation

Generate a formatted changelog entry from recent git commits.

Steps

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

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

  3. 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:)

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

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

  6. 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.
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. 2mo ago First seen · 62 lines · 82 tokens per session scan A ddb24608bda6

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository ao92265/claude-code-playbook (13 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 603 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-31.

Claude CodeGit and workflowLLMReleasesai-agentsdeveloper-toolshooksprompt-engineering
Related

changelog compared with skills from other repositories

changelog next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
changelogao92265/claude-code-playbookSkill13todayMITA82Claude Code
launchsimota/agent-skillsSkill99yesterdayMITA40Claude Code, Codex
release-checklistlizhiyao/oh-my-knowledgeSkill25todayMITA13Claude Code, Codex
lfe-archivistStChiotis/Library-First-EngineeringSkill444mo agoMITA40Claude Code, Codex
rea-changelog-updateroedyrustam/vibes-plugSkill1262d agoMITA34Cursor
publish-oss-repoiamakbarsha1/whetstoneSkill419d agoCC-BY-4.0A91Claude Code
finishing-a-development-branchnaimkatiman/continuous-improvementSkill912d agoMITA27Claude Code