agentmods.dev

changelog-generator

changelog-generator is a skill for Claude Code, Codex from skrun-dev/skrun. It costs 68 tokens per session (792 once invoked), scanned A, original, MIT.

A release-writing tool that turns a Git repository's commit history into a CHANGELOG.md file and a release-notes.md document.

In plain words
What is it for?
Use it to summarize changes between Git tags or create notes for an upcoming release.
Why use it?
It saves maintainers from reading and rewriting many commits into updates that users can understand.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 210repo 27d ago A scan SkillSpector: pass 68 tokens original MIT

Good fit Use it to summarize changes between Git tags or create notes for an upcoming release.

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

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/skrun-dev/skrun/changelog-generator/github.svg)](https://agentmods.dev/skills/skrun-dev/skrun/changelog-generator)
Your own site
<a href="https://agentmods.dev/skills/skrun-dev/skrun/changelog-generator"><img src="https://agentmods.dev/badge/skills/skrun-dev/skrun/changelog-generator/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-generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/skrun-dev/skrun/changelog-generator"><img src="https://agentmods.dev/badge/skills/skrun-dev/skrun/changelog-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 792 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00068 $0.00792
Opus 5.5 $0.00027 $0.00317
Sonnet 5.5 $0.00014 $0.00158
Haiku 4.5 $0.00007 $0.00079

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

Security

Grade A, and why

changelog-generator 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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/git_log.ts, scripts/write_artifact.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

agents/changelog-generator/SKILL.md · 43 lines

How it starts

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

Changelog Generator

You are a release-notes ghostwriter for OSS maintainers. Given a local git history, you produce two artifacts: a CHANGELOG.md (Keep a Changelog format) and a release-notes.md (blog-style narrative).

Workflow

  1. Read commits — call the git_log tool with source set to the user's repo_path. Pass from_ref and to_ref if the user supplied from_tag / to_tag. Use the default limit: 200 unless the user explicitly asked for more.
  2. Group commits by Conventional Commit type — parse each commit subject. The leading prefix before : (or (scope):) determines the type:
    • feat: or feat(scope): → Added
    • fix: or fix(scope): → Fixed
    • chore:, refactor:, style:, test: → Changed
    • docs: → Documentation
    • Any subject containing BREAKING CHANGE, breaking:, or !: → Breaking (highest priority — breaking commits go in their own section even if they have another type)
    • Anything else → Other
  3. Compose CHANGELOG.md — Keep a Changelog format. Header: # Changelog. Then one section per release range (use to_tag or "Unreleased" if HEAD). Inside each release, the bucket order is: Breaking → Added → Changed → Fixed → Documentation → Other. Each commit is a bullet: - <subject> ([hash](#)). Skip empty buckets.
  4. Compose release-notes.md — narrative blog format. Header: # <project_name> <to_tag> (or "Unreleased"). Open with a 2–3 sentence paragraph summarizing what's most exciting. Then one short paragraph per non-empty bucket, hand-written prose (don't just list commits — synthesize). Close with a "Thanks to ..." line listing the unique authors.
  5. Write both files — call write_artifact once with filename: "CHANGELOG.md" and once with filename: "release-notes.md".
  6. Return structured output:
    • summary: the narrative paragraph from release-notes.md (1 paragraph, ~3 sentences)
    • commit_count: total commits processed
    • groups: object with counts per type (e.g., { "feat": 12, "fix": 7, "chore": 3, "breaking": 1, "docs": 2, "other": 0 })

Read the full file on GitHub · 43 lines

Files

What ships with it

5 files 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. 1mo ago First seen · 43 lines · 68 tokens per session scan A 2a66654801c7

Subscribe to this mod's changes

changelog-generator is a skill published in the GitHub repository skrun-dev/skrun (210 stars, last pushed 27d ago), licensed MIT. It adds 68 tokens to every session and 792 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-30.

Git and workflowLLMReleasesWriting and docsagent-skillsai-agentsapiclimcp
Related

Other skills, from other repositories

pi-package-sandbox-test

Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.

spences10/my-pi · 40 tokens

pypi-release

This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.

alchemiststudiosDOTai/tunacode · 52 tokens

git

Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…

bug-ops/zeph · 106 tokens

github

GitHub CLI (gh) for repository management, issues, pull requests, releases, workflows, search, gists, and API access. Use when the user asks about any GitHub operation — creating repos, forking, cloning, PR workflows, issue triage, CI/CD runs, code search, release management, or direct API calls. Keywords: github, gh…

bug-ops/zeph · 104 tokens

pi-release-workflow

Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.

spences10/my-pi · 38 tokens

pi-review-gated-delivery

Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.

spences10/my-pi · 40 tokens