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 FradSer/dotclaude --skill update-changeloggit clone --depth 1 https://github.com/FradSer/dotclaudeWrote 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/fradser/dotclaude/update-changelog)<a href="https://agentmods.dev/skills/fradser/dotclaude/update-changelog"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/update-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/fradser/dotclaude/update-changelog"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/update-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.00076 | $0.01502 |
| Opus 5.5 | $0.00030 | $0.00601 |
| Sonnet 5.5 | $0.00015 | $0.00300 |
| Haiku 4.5 | $0.00008 | $0.00150 |
Grade A, and why
update-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 22d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Changelog
Create or update CHANGELOG.md following the Keep a Changelog 1.1.0 format, using git tags as version boundaries.
CRITICAL: Human-First Entries and Format
- Do NOT copy commit messages verbatim. Changelogs are for humans -- readers who care about what changed and why, not how the code was modified. Group related commits into logical changes and write each entry as a clear, meaningful description.
- The
[Unreleased]section MUST always be present, even if empty. - Versions MUST be in reverse chronological order (newest first), with ISO 8601 dates (
YYYY-MM-DD). - Omit empty categories -- only include categories that have entries.
- When updating an existing changelog, preserve any hand-edited entries in existing version sections -- do not overwrite them.
See references/keepachangelog-format.md for the full format specification.
Process
1. Gather git tag and remote info
Run these commands to understand the project's release history:
git tag --sort=-v:refname
git log --oneline --decorate
git remote get-url origin
Collect:
- All tags sorted by version (descending). Both
v1.0.0and1.0.0prefixes are valid -- detect which convention the project uses and stay consistent. - The remote URL to construct diff comparison links.
- The hosting platform (GitHub, GitLab, Bitbucket) to pick the correct comparison URL pattern.
If no tags exist, inform the user and generate only an [Unreleased] section from the full commit history.
2. Check for existing CHANGELOG.md
Look for CHANGELOG.md (case-insensitive) in the project root.
- Exists: Read it. Preserve any hand-written content. Only add or update version sections that are missing or incomplete.
- Does not exist: Create a new file from scratch.
3. Build version sections from git history
For each pair of adjacent tags (newest to oldest), extract commits with their full messages:
git log --format="%h %s%n%b" <older-tag>..<newer-tag>
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.
- 22d ago First seen · 165 lines · 76 tokens per session scan A 14561684298f
update-changelog is a skill published in the GitHub repository FradSer/dotclaude (593 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 1,502 once invoked, about $0.0003 per session on Opus 5.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-09-24.
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.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
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.