agentmods.dev

changelog-mcp: Skill for Claude Code

.claude/skills/changelog/SKILL.md

changelog is a skill for Claude Code from smartsys/changelog-mcp. It costs 46 tokens per session (1,657 once invoked), scanned A, original, MIT.

A helper for recording changes in a project's changelog, a dated list of notable updates. It examines the current Git changes and follows the project's configured changelog format.

In plain words
What is it for?
For creating changelog entries after code changes, when the project has been initialized for changelog storage.
Why use it?
It turns completed implementation work into a consistent record instead of requiring you to write the entry from scratch.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is smartsys/changelog-mcp's own configuration. It tells Claude Code how to work on changelog-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything changelog-mcp configures →

not rated 0repo 13d ago A scan 46 tokens original MIT
View source ↗ smartsys/changelog-mcp
Reuse

Borrowing it

Nothing to install: this file belongs to smartsys/changelog-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/smartsys/changelog-mcp/main/.claude/skills/changelog/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/smartsys/changelog-mcp

Made for: Claude Code.

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/smartsys/changelog-mcp/changelog/github.svg)](https://agentmods.dev/skills/smartsys/changelog-mcp/changelog)
Your own site
<a href="https://agentmods.dev/skills/smartsys/changelog-mcp/changelog"><img src="https://agentmods.dev/badge/skills/smartsys/changelog-mcp/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/smartsys/changelog-mcp/changelog"><img src="https://agentmods.dev/badge/skills/smartsys/changelog-mcp/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,657 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.00046 $0.01657
Opus 5 $0.00023 $0.00829
Sonnet 5 $0.00009 $0.00331
Haiku 4.5 $0.00005 $0.00166

Measured 11d ago against content hash 27de6cdba761, 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.

.claude/skills/changelog/SKILL.md · 133 lines

How it starts

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

/changelog

Erstellt einen Changelog-Eintrag für die aktuelle Arbeit.

Voraussetzung: einmal init_changelog

Vor dem ersten Changelog-Eintrag müssen Store und Config existieren. Sind sie noch nicht angelegt — oder meldet ein Tool „Konfiguration fehlt" bzw. „In CHANGELOG_MCP_CONFIG angegebene Konfiguration fehlt" — einmal init_changelog ausführen. Es legt Store und Config-Datei an (am Pfad aus CHANGELOG_MCP_CONFIG, sonst im Projekt-Root) und ist idempotent: ein zweiter Aufruf überschreibt nichts. Das gilt pro Projekt — es gibt keinen globalen Changelog.

Execution

User provided context: "$ARGUMENTS"

Schritt 1: Änderungen analysieren

Analysiere was in der aktuellen Session geändert wurde:

  1. git status - Ungetrackte und geänderte Dateien
  2. git diff HEAD - Aktuelle Änderungen
  3. git log --oneline -5 - Letzte Commits für Kontext

Falls keine Änderungen vorhanden sind, frage den User was dokumentiert werden soll.

Schritt 2: Changelog-Eintrag vorbereiten

Bestimme aus den Änderungen:

  • Kategorie: hängt vom aktiven Format ab (get_config zeigt es). Achtung: keep-a-changelog und conventional validieren strikt — eine unbekannte Kategorie lässt add_entry fehlschlagen:
    • smart (Default): frei wählbar. Empfehlung: Added, Changed, Deprecated, Removed, Fixed, Security, Documentation.
    • keep-a-changelog (strikt): nur Added, Changed, Deprecated, Removed, Fixed, Security.
    • conventional (strikt): nur Features, Bug Fixes, Performance, Reverts, Breaking Changes.
  • Beschreibung: Kurze Zusammenfassung der Änderung (1 Zeile)
  • Details: Technische Details als Liste
  • Dateien: Geänderte Dateien mit Beschreibung
  • Version-Bump: bump = patch (Default, Fehlerbehebung/Kleinigkeit), minor (neue, abwärtskompatible Funktion) oder major (Breaking Change). Wirkt nur im Modus semver; bei patch-only wird bump ignoriert (nur die Patch-Stelle zählt hoch).
  • Privat?: private=true setzen, wenn die Änderung nicht-öffentliche Doku/interne Arbeit betrifft, die nicht im publizierten Changelog erscheinen soll. Im Zweifel nachfragen.

Read the full file on GitHub · 133 lines

Files

What ships with it

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

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 · 133 lines · 46 tokens per session scan A 27de6cdba761

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository smartsys/changelog-mcp (0 stars, last pushed 13d ago), licensed MIT. It adds 46 tokens to every session and 1,657 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.

Git and workflowReleaseschangelogchangelog-generatordeveloper-toolsmcpversioning-api
Related

Other skills, from other repositories

doc-refresh

Orchestrates documentation updates after version bumps, feature additions, or periodic maintenance. Analyses git history since the last release, identifies which docs are affected, and delegates to existing skills (changelog, feature-benefits, docs-verify, llms-txt, user-guides) for selective refresh. Delegates AI…

littlebearapps/pitchdocs · 86 tokens

changelog

Generates user-friendly changelogs from git history using conventional commits. Writes entries in benefit language ("You can now..." not "Refactored internal..."). Follows Keep a Changelog format. Use when creating or updating CHANGELOG.md.

littlebearapps/pitchdocs · 52 tokens

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.

paperclipai/paperclip · 42 tokens

github-release-briefing-skill

Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.

FrancyJGLisboa/agent-skill-creator · 45 tokens

taiyi-integration

A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.

Dong90/oh-my-taiyiforge · 27 tokens

changelog-gen

A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.

laolaoshiren/claude-code-skills-zh · 19 tokens