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 reidemeister94/development-skills --skill changeloggit clone --depth 1 https://github.com/reidemeister94/development-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/reidemeister94/development-skills/changelog)<a href="https://agentmods.dev/skills/reidemeister94/development-skills/changelog"><img src="https://agentmods.dev/badge/skills/reidemeister94/development-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/reidemeister94/development-skills/changelog"><img src="https://agentmods.dev/badge/skills/reidemeister94/development-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.00026 | $0.00613 |
| Opus 5 | $0.00013 | $0.00307 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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 10d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
changelog
Manage CHANGELOG.md per Keep a Changelog 1.1.0 and SemVer 2.0.0:
- add: one entry;
- from-commits: derive entries from Conventional Commits;
- release: cut a version.
Edit only CHANGELOG.md. Never change version files, commit, or tag; release prints suggested commands.
Step 1 — Resolve the action
Resolve add, from-commits (commits), or release from $ARGUMENTS or the request; ask if ambiguous.
Step 2 — Pre-flight (all actions)
root=$(git rev-parse --show-toplevel 2>/dev/null) || root=.
ls "$root/CHANGELOG.md" 2>/dev/null
Always use $root/CHANGELOG.md, never a cwd-relative path.
- Existing: read and preserve style.
- Missing for
add/from-commits: create the standard linked title, intro, and## [Unreleased]skeleton. - Missing for
release: stop and suggest/changelog addor/changelog from-commits.
Step 3 — Insert under [Unreleased] (add, from-commits)
Append - <imperative description> to its category under [Unreleased], creating the category in canonical order. Never edit released sections or date [Unreleased].
Step 4 — Run the action
Load writing guidelines for entry rules, commit mapping, and SemVer bumps.
- add — use the user's text or ask for one of the six categories and a ≤15-word description; tighten and insert it.
- from-commits — follow the process below.
- release — follow
references/release.md.
from-commits
The changelog, not git tags, is the source of truth for what shipped — derive entries, don't mirror the log.
- Range: use
<latest-tag>..HEAD; without tags, find the commit for the latest released section. Without either baseline, show the commit count and ask for all, last 30, last 100, or another range. Never silently choose all. - Gather: inspect subjects and bodies; breaking footers may be in bodies.
- Derive: map, filter, aggregate, and deduplicate per the guidelines. Collapse a 10–20-commit feature into 1–3 user-facing entries.
- Confirm: show grouped proposals plus skipped or aggregated items with reasons, then insert only after approval.
What ships with it
2 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.
- 10d ago First seen · 55 lines · 26 tokens per session scan A a41a145f4fdd
changelog is a skill published in the GitHub repository reidemeister94/development-skills (11 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 613 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-08-30.
Other skills, from other repositories
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
changelog
A tool for writing release notes from a structured record of changes that actually shipped. Release notes summarize changes for people who use or maintain the product.
ship
/ship - Release Pipeline Commander.
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.