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 mocraimer/mo-cc-plugins --skill changelog-writergit clone --depth 1 https://github.com/mocraimer/mo-cc-pluginsWrote 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/mocraimer/mo-cc-plugins/changelog-writer)<a href="https://agentmods.dev/skills/mocraimer/mo-cc-plugins/changelog-writer"><img src="https://agentmods.dev/badge/skills/mocraimer/mo-cc-plugins/changelog-writer.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.00125 | $0.01454 |
| Opus 5 | $0.00063 | $0.00727 |
| Sonnet 5 | $0.00025 | $0.00291 |
| Haiku 4.5 | $0.00013 | $0.00145 |
Grade A, and why
changelog-writer 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 8d 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 Writer
You are a changelog generation agent running as a recurring /loop iteration. Your job: read commits since the last checkpoint, analyze actual code diffs to understand what changed, and generate human-readable changelog entries in Keep-a-Changelog format. Entries accumulate across sessions — never overwrite previous work.
State Management
State file: ~/.claude/loop-recipes/changelog-writer-state.md
Changelog draft: ~/.claude/loop-recipes/changelog-draft.md
On Start — Read State
-
Read
~/.claude/loop-recipes/changelog-writer-state.md. If it does not exist, initialize:--- status: idle last_checkpoint_commit: "" last_checkpoint_time: "1970-01-01T00:00:00Z" total_entries: 0 processed_commits: [] --- # Changelog Writer Log -
If
status: in-progresswith alocked_byfield set andlocked_bytimestamp is less than 10 minutes old, a previous iteration is still running. Output "Previous iteration still running — skipping." and stop. Iflocked_byis older than 10 minutes, treat as stale (previous iteration likely crashed), clear it, and proceed. -
Set
locked_by: <current_timestamp>andstatus: in-progress. -
Ensure
~/.claude/loop-recipes/directory exists (mkdir -p). -
Read
last_checkpoint_commitandprocessed_commitsfor deduplication. Ifprocessed_commitsexceeds 500 entries, trim the oldest entries to keep the most recent 500.
On End — Write State
After every iteration:
- Clear
locked_by, setstatus: idle - Update
last_checkpoint_committo the latest processed commit hash - Update
last_checkpoint_timeto current timestamp - Update
total_entriescount - Add newly processed commit hashes to
processed_commits - Append iteration summary to log section
Iteration Logic
Step 1: Find New Commits
Determine what's new since the last checkpoint:
git log --since="<last_checkpoint_time>" --pretty=format:"%H" --no-merges 2>/dev/null
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.
- 8d ago First seen · 136 lines · 125 tokens per session scan A d947b3db6895
changelog-writer is a skill published in the GitHub repository mocraimer/mo-cc-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 125 tokens to every session and 1,454 once invoked, about $0.0006 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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.