agentmods.dev

changelog

changelog is a skill for Claude Code from rikdc/ai-skills. It costs 45 tokens per session (799 once invoked), scanned A, original, MPL-2.0.

A tool for maintaining a CHANGELOG.md file, a running record of notable project changes, using the Keep a Changelog format and Semantic Versioning.

In plain words
What is it for?
Use it to create a changelog, add entries under categories such as added or fixed, and prepare a versioned release entry.
Why use it?
It keeps release notes organized and prevents inconsistent headings or accidental overwriting of an existing changelog.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the git-workflow plugin — 3 skills shipped together

not rated 2repo 5d ago A scan 45 tokens original MPL-2.0

Good fit Use it to create a changelog, add entries under categories such as added or fixed, and prepare a versioned release entry.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rikdc/ai-skills/changelog
View source ↗ rikdc/ai-skills
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 rikdc/ai-skills --skill changelog
Clone the repo
git clone --depth 1 https://github.com/rikdc/ai-skills

Made for: Claude Code.

Or install git-workflow, the plugin that ships this one along with the rest of its 3 skills.

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/rikdc/ai-skills/changelog/github.svg)](https://agentmods.dev/skills/rikdc/ai-skills/changelog)
Your own site
<a href="https://agentmods.dev/skills/rikdc/ai-skills/changelog"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/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/rikdc/ai-skills/changelog"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 799 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.00045 $0.00799
Opus 5 $0.00023 $0.00400
Sonnet 5 $0.00009 $0.00160
Haiku 4.5 $0.00005 $0.00080

Measured 11d ago against content hash e571926e6e29, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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.

plugins/git-workflow/skills/changelog/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Changelog - Keep a Changelog Maintenance

Maintains CHANGELOG.md in Keep a Changelog format with Semantic Versioning.

Usage

  • /git-workflow:changelog --create - Create CHANGELOG.md
  • /git-workflow:changelog --add-entry "description" --type TYPE - Add an entry
  • /git-workflow:changelog --release X.Y.Z - Cut a release

With no flags, infer the operation from the request. Categories: added, changed, deprecated, removed, fixed, security.

Skeleton

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

## [1.2.3] - 2024-01-15

### Added

- User authentication

Category headings exist only where they have entries. Never write a heading with a placeholder bullet under it.

Operation: --create

  1. Read CHANGELOG.md. If it exists, stop and report it — do not overwrite.
  2. Write the skeleton above with an empty ## [Unreleased] and no version sections.
  3. Offer to seed it from git log, but do not do so unasked.

Operation: --add-entry

  1. Read CHANGELOG.md; run --create first if it is missing.
  2. Reject a --type outside the six categories.
  3. Append the entry as a bullet under ## [Unreleased] and its ### <Type> heading, adding that heading if absent.
  4. Preserve the existing order of categories and the file's surrounding formatting.

Operation: --release X.Y.Z

Check before writing, and stop with the reason if any fails:

  • ## [Unreleased] has at least one entry — nothing to release otherwise.
  • X.Y.Z does not already appear in the file.
  • X.Y.Z is higher than the most recent version present.

Then:

  1. Get today's date with date +%F. Do not guess it.
  2. Rename ## [Unreleased] to ## [X.Y.Z] - YYYY-MM-DD, keeping its entries.
  3. Insert a fresh empty ## [Unreleased] above it.
  4. If the file uses link references at the bottom, add one for X.Y.Z and repoint [Unreleased] to compare against the new tag.

Read the full file on GitHub · 85 lines

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. 11d ago First seen · 85 lines · 45 tokens per session scan A e571926e6e29

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 5d ago), licensed MPL-2.0. It adds 45 tokens to every session and 799 once invoked, about $0.0002 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.

Claude CodeGit and workflowReleasesclaude-code-plugin
Related

Other skills, from other repositories

skill-ship

Package and finalize completed work for delivery — use when a feature is done and ready to ship.

nyldn/claude-octopus · 22 tokens

deploy-steward

Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.

SethGammon/Citadel · 56 tokens

release

CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.

oliver-kriska/claude-elixir-phoenix · 60 tokens

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens

last-tag

Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.

umputun/cc-thingz · 50 tokens

han-release

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…

testdouble/han · 172 tokens