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 samuelgudi/iknowkungfu --skill keep-a-changeloggit clone --depth 1 https://github.com/samuelgudi/iknowkungfuWrote 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/samuelgudi/iknowkungfu/keep-a-changelog)<a href="https://agentmods.dev/skills/samuelgudi/iknowkungfu/keep-a-changelog"><img src="https://agentmods.dev/badge/skills/samuelgudi/iknowkungfu/keep-a-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/samuelgudi/iknowkungfu/keep-a-changelog"><img src="https://agentmods.dev/badge/skills/samuelgudi/iknowkungfu/keep-a-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.00057 | $0.01292 |
| Opus 5 | $0.00028 | $0.00646 |
| Sonnet 5 | $0.00011 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
keep-a-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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
keep-a-changelog
A changelog is a curated, human-readable list of notable changes per release. It is not a git log. The git log is a complete, machine-generated record of every commit; a changelog is a deliberate, edited summary of what a user of the project needs to know. Conflating the two produces a changelog nobody reads.
This skill follows the Keep a Changelog convention.
Use this skill when
- A project has no
CHANGELOG.mdand you are adding one. - You are about to cut a release and need to turn the accumulated changes into release notes.
- You made a notable change and need to decide whether — and where — it goes in the changelog.
Core principles
- For humans, by humans. Every entry is written for a person deciding whether to upgrade and what will change for them. "Bumped dependency X" matters only if it changes observable behaviour.
- One section per version. Reverse chronological — newest at the top.
- An
[Unreleased]section at the very top. This is where entries land as the work happens. At release time it gets a version number and a date; a fresh empty[Unreleased]takes its place. - Dates in ISO 8601 (
YYYY-MM-DD). Unambiguous across locales. - Notable, not exhaustive. Internal refactors, formatting, test-only changes, and CI tweaks usually do not belong. If it does not change what a user can observe, leave it out.
The six categories
Every entry goes under exactly one of these headings. They are fixed — do not invent new ones.
| Heading | For |
|---|---|
Added |
New features, new public surface. |
Changed |
Changes to existing behaviour. |
Deprecated |
Features still present but slated for removal — warn users now. |
Removed |
Features taken out in this release. |
Fixed |
Bug fixes. |
Security |
Fixes for vulnerabilities. Call these out so users know to upgrade urgently. |
Within a version, list only the categories that actually have entries. A release with just bug fixes has only a Fixed heading.
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.
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 · 103 lines · 57 tokens per session scan A 62de8a220af8
keep-a-changelog is a skill published in the GitHub repository samuelgudi/iknowkungfu (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,292 once invoked, about $0.0003 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.