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 definite-d/agent-skills --skill changeloggit clone --depth 1 https://github.com/definite-d/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/definite-d/agent-skills/changelog)<a href="https://agentmods.dev/skills/definite-d/agent-skills/changelog"><img src="https://agentmods.dev/badge/skills/definite-d/agent-skills/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/definite-d/agent-skills/changelog"><img src="https://agentmods.dev/badge/skills/definite-d/agent-skills/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.00235 | $0.01556 |
| Opus 5 | $0.00118 | $0.00778 |
| Sonnet 5 | $0.00047 | $0.00311 |
| Haiku 4.5 | $0.00023 | $0.00156 |
Grade A, and why
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 9d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Skill
Produce human-readable, release-ready changelogs that follow Keep a Changelog structure and Semantic Versioning bump rules, whether starting from an empty repo or maintaining an existing file.
Mode Selection
| Mode | Trigger | Action |
|---|---|---|
| From scratch | No CHANGELOG.md exists |
Build full file from git history / records |
| Update existing | CHANGELOG.md exists |
Merge new changes, preserving its conventions |
| Subset | User names a version range | Extract only that window |
Confirm the mode and target (whole repo, a package, a file) before writing.
Gather Records
Prioritize sources in this order:
- Existing changelog — parse headings, section names, date format, link style. Preserve them.
- Git history — scope per mode:
git tag --sort=-version:refname # release anchors git log <last_tag>..HEAD --oneline --decorate # unreleased changes git log --oneline --decorate # full history (from scratch) git log -1 --format='%ad %h' --date=short <tag> # release date for a tag - Release records — release notes, PR descriptions, issues closed in a milestone. Treat as ground truth when present; use commits to fill gaps.
- User-provided lists — commit messages pasted in chat. Parse them as-is.
Skip merge commits, dependabot noise, and generated files unless they affect users.
Bucket Into Standard Sections
Keep a Changelog categories, ordered as shown:
| Section | Conventional type mapping | Example entry |
|---|---|---|
| Added | feat, perf (new) |
- **Added:** rate_limit middleware for public endpoints. |
| Changed | refactor, perf, style |
- **Changed:** JSON serialization to use orjson. |
| Fixed | fix |
- **Fixed:** panic on empty payload in the webhook handler. |
| Removed | remove, revert, deprecate follow-up |
- **Removed:** legacy v1 auth endpoints. |
| Deprecated | deprecate |
- **Deprecated:** --envflag; use--profile instead. |
| Security | fix (CVE), security |
- **Security:** patched SSRF in proxy URL validation. |
What ships with it
3 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.
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.
- 9d ago First seen · 136 lines · 235 tokens per session scan A 46094278c4c5
changelog is a skill published in the GitHub repository definite-d/agent-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 235 tokens to every session and 1,556 once invoked, about $0.0012 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
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.