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 skills add matteocervelli/llms --skill changelog-generatorgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/changelog-generator)<a href="https://agentmods.dev/skills/matteocervelli/llms/changelog-generator"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/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.
<a href="https://agentmods.dev/skills/matteocervelli/llms/changelog-generator"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/changelog-generator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00028 | $0.04537 |
| Opus 5 | $0.00014 | $0.02269 |
| Sonnet 5 | $0.00006 | $0.00907 |
| Haiku 4.5 | $0.00003 | $0.00454 |
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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 706 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CHANGELOG Generator Skill
Purpose
This skill provides systematic guidance for generating CHANGELOG entries that follow conventional commits format and semantic versioning principles, ensuring clear and consistent change history documentation.
When to Use
- After feature implementation and documentation updates
- Need to document changes for users and developers
- Following conventional commits format
- Determining semantic version increments
- Creating release notes
CHANGELOG Generation Workflow
1. Analyze Changes
Objective: Understand what changed in this feature/fix.
Review commit history:
# View commits since last release/main
git log --oneline main..HEAD
# View detailed commits
git log main..HEAD
# View files changed
git diff --stat main..HEAD
# View actual changes
git diff main..HEAD
Identify change types:
- New features added
- Bug fixes implemented
- Documentation updates
- Performance improvements
- Security enhancements
- Breaking changes
- Deprecations
Review issue and PR:
- Read original issue description
- Review acceptance criteria
- Check PR description
- Note any breaking changes
- Identify security implications
Deliverable: Clear understanding of all changes
2. Determine Change Type
Objective: Classify the change according to conventional commits.
Conventional Commit Types:
| Type | Description | Version Impact | Use When |
|---|---|---|---|
feat |
New feature | MINOR (0.X.0) | Adding new functionality |
fix |
Bug fix | PATCH (0.0.X) | Fixing a bug |
docs |
Documentation | PATCH (0.0.X) | Only docs changed |
style |
Code style | PATCH (0.0.X) | Formatting, whitespace |
refactor |
Code refactoring | PATCH (0.0.X) | Code restructure, no behavior change |
perf |
Performance | PATCH (0.0.X) | Performance improvements |
test |
Tests | PATCH (0.0.X) | Adding/updating tests |
chore |
Maintenance | PATCH (0.0.X) | Build, deps, configs |
BREAKING CHANGE |
Breaking change | MAJOR (X.0.0) | Incompatible API 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.
- 7d ago First seen · 706 lines · 28 tokens per session scan A 22f1c67bd5ae
changelog-generator is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 4,537 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.