Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/mountainunicorn/add/changelog)<a href="https://agentmods.dev/skills/mountainunicorn/add/changelog"><img src="https://agentmods.dev/badge/skills/mountainunicorn/add/changelog.svg" alt="Measured on agentmods" 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.00016 | $0.01541 |
| Opus 5 | $0.00008 | $0.00771 |
| Sonnet 5 | $0.00003 | $0.00308 |
| Haiku 4.5 | $0.00002 | $0.00154 |
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 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADD Changelog Command v{{VERSION}}
Generate or refresh the project's CHANGELOG.md from git history using conventional commit parsing. Follows the Keep a Changelog format.
Pre-Flight Check
- Check if
CHANGELOG.mdexists in the project root - If it does NOT exist, create it from
${CLAUDE_PLUGIN_ROOT}/templates/changelog.md.template - Read
.add/config.jsonforchangelog.lastProcessedCommit(may be null) - Determine mode:
--from-scratchflag means full regeneration; otherwise incremental
Conventional Commit Mapping
Map conventional commit prefixes to Keep a Changelog sections:
| Commit Prefix | Changelog Section |
|---|---|
| feat: | Added |
| fix: | Fixed |
| docs: | Documentation |
| refactor: | Changed |
| perf: | Changed |
| deprecate: | Deprecated |
| remove: | Removed |
| security: | Security |
| revert: | Fixed |
Excluded Prefixes (not added to changelog)
These are internal/maintenance commits and should be silently skipped:
chore:test:ci:style:build:
Non-Conventional Commits
Commits that do not match any conventional prefix are categorized under Changed with the full message as the entry text.
Merge Commits
Skip merge commits entirely — they duplicate the content of the merged commits.
Phase 1: Gather Commits
Incremental Mode (default)
- Read
CHANGELOG.mdto understand current state - Read
.add/config.jsonforchangelog.lastProcessedCommit - If
lastProcessedCommitis set:- Run
git log --oneline --no-merges {lastProcessedCommit}..HEADto get new commits
- Run
- If
lastProcessedCommitis null:- Run
git log --oneline --no-mergesto get all commits
- Run
- If no new commits found, report "Changelog is up to date" and exit
From-Scratch Mode (--from-scratch)
- Run
git tag --sort=-version:refnameto get all version tags - Run
git log --oneline --no-mergesto get full commit history - Group commits by version tags:
- Commits after the latest tag go in
[Unreleased] - Commits between tags go in
[tag] - datesections (use tag date) - Commits before the earliest tag go in the earliest version section
- Commits after the latest tag go in
- Regenerate
CHANGELOG.mdentirely (preserve the header from template)
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 · 172 lines · 16 tokens per session scan A c908d9337072
changelog is a skill published in the GitHub repository MountainUnicorn/add (11 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,541 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
checkpoint
Save a checkpoint — bump version, commit, push. Use when work is complete and ready to ship without the full finish protocol.
bump
Bumping project version and updating changelog atomically. Use when releasing a new version — patch, minor, or major.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
last-tag
Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.