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 kellykampen/agent-skills --skill add-to-changeloggit clone --depth 1 https://github.com/kellykampen/agent-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/kellykampen/agent-skills/add-to-changelog)<a href="https://agentmods.dev/skills/kellykampen/agent-skills/add-to-changelog"><img src="https://agentmods.dev/badge/skills/kellykampen/agent-skills/add-to-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.
<a href="https://agentmods.dev/skills/kellykampen/agent-skills/add-to-changelog"><img src="https://agentmods.dev/badge/skills/kellykampen/agent-skills/add-to-changelog.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.00092 | $0.00630 |
| Opus 5 | $0.00046 | $0.00315 |
| Sonnet 5 | $0.00018 | $0.00126 |
| Haiku 4.5 | $0.00009 | $0.00063 |
Grade A, and why
add-to-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 12d 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
Add to Changelog
Add a new entry to the project's CHANGELOG.md following the Keep a Changelog format and Semantic Versioning.
Arguments
<version>— SemVer version (e.g.1.1.0,2.0.0-beta.1)<change_type>— one of:added,changed,deprecated,removed,fixed,security<message>— description of the change (quote multi-word messages)
If any argument is missing, infer sensible values from context (e.g. the current work) or ask the user.
Process
- Parse the version, change type, and message from the arguments.
- Check if
CHANGELOG.mdexists in the project root. If not, create it with the standard Keep a Changelog header:# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/), and this project adheres to [Semantic Versioning](https://semver.org/). - Look for an existing
## [<version>]section.- If it exists, add the entry under the appropriate
### <Change Type>heading (create the heading if absent). - If it doesn't, create a new version section with today's date:
## [<version>] - YYYY-MM-DD(get the date fromdate +%F), then the change-type heading and entry.
- If it exists, add the entry under the appropriate
- Keep versions in reverse-chronological order and entries tidy.
- Write the file back.
Change types
- Added — new features
- Changed — changes to existing functionality
- Deprecated — soon-to-be-removed features
- Removed — removed features
- Fixed — bug fixes
- Security — security fixes
Example
/add-to-changelog 1.1.0 added "Waitlist referral source configuration" →
## [1.1.0] - 2026-01-15
### Added
- Waitlist referral source configuration
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.
- 12d ago First seen · 63 lines · 92 tokens per session scan A 64f4e62fac7e
add-to-changelog is a skill published in the GitHub repository kellykampen/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 630 once invoked, about $0.0005 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.