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 agentmods add skills/luqiang-code/claude-code-skills/changelog-generatornpx skills add luqiang-code/claude-code-skills --skill changelog-generatorgit clone --depth 1 https://github.com/luqiang-code/claude-code-skillsWrote 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/luqiang-code/claude-code-skills/changelog-generator)<a href="https://agentmods.dev/skills/luqiang-code/claude-code-skills/changelog-generator"><img src="https://agentmods.dev/badge/skills/luqiang-code/claude-code-skills/changelog-generator.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00561 |
| Opus 5 | $0.00016 | $0.00280 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
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 5d 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 Generator
Generate a Keep a Changelog-formatted CHANGELOG.md from git history.
When to Use
- Preparing a release and need release notes
- User mentions "changelog", "release notes"
- Project follows Conventional Commits
When NOT to Use
- First commit of a project (no history yet)
- Non-Conventional Commits repos (output will be poorly categorized)
Workflow
- Determine the version range: ask user for
fromandtotags/commits - Run
git log <from>..<to> --onelineto get commits in range - Categorize commits by Conventional Commit type:
feat→ Addedfix→ Fixedperf→ Changed (performance)refactor→ Changeddocs→ (skip for changelog, user-facing only)BREAKING CHANGE→ Changed (breaking)
- Group by category, format as bullet list
- Prepend to existing CHANGELOG.md or create new one
- Add version header with date
Output Format
# Changelog
## [1.2.0] - 2026-05-29
### Added
- JWT refresh token rotation (#234)
- Rate limiting on login endpoint (#235)
### Fixed
- Race condition in order status update (#231)
- Memory leak in WebSocket connection handler (#228)
### Changed
- **Breaking:** Refresh token response format updated
- Improved database connection pool management
Key Principles
- Follow Keep a Changelog format
- Human-readable descriptions, not raw commit messages
- Group by impact: Added → Fixed → Changed → Deprecated → Removed → Security
- Link to issue/PR numbers when available
- Breaking changes MUST be clearly marked
Notes
- Skip chore/test/docs commits (not user-facing)
- If no tag exists, use the first and last commit of the range
- Confirm version number and date before writing
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.
- 5d ago First seen · 79 lines · 33 tokens per session scan A 1a75d5953dc6
changelog-generator is a skill published in the GitHub repository luqiang-code/claude-code-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 561 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.
Other skills, from other repositories
doc-changelog
CHANGELOG maintenance following Keep a Changelog. Trigger when the user wants to document changes or prepare a release.
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
golden-chat-topics
Use when testing the goldenchattopics golden build.
golden-chat-single
Use when testing the goldenchatsingle golden build.
golden-rss-empty
Use when testing the empty rss golden build.