Borrowing it
Nothing to install: this file belongs to brizzai/fleet. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brizzai/fleet/master/.claude/skills/update-changelog/SKILL.mdgit clone --depth 1 https://github.com/brizzai/fleetWrote 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/brizzai/fleet/update-changelog)<a href="https://agentmods.dev/skills/brizzai/fleet/update-changelog"><img src="https://agentmods.dev/badge/skills/brizzai/fleet/update-changelog.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00660 |
| Opus 5 | $0.00000 | $0.00330 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
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 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Current Branch Context
!git log --oneline $(git merge-base HEAD master)..HEAD 2>/dev/null || echo "no commits"
!git diff --name-only $(git merge-base HEAD master)..HEAD 2>/dev/null || echo "no changes"
Task
Add a changelog fragment for this PR, or skip with /no-changelog.
This repo does not hand-edit CHANGELOG.md. Each PR drops a small fragment
file in changelog/unreleased/; at release time (/ship) they're merged into
CHANGELOG.md and deleted automatically. Full guide + voice: changelog/README.md.
If argument is "skip", "no-changelog", or "none"
Comment /no-changelog on the PR and stop:
gh pr comment --body "/no-changelog"
Otherwise, add a fragment
- Create
changelog/unreleased/<short-name>.md(any unique kebab-case name). - Frontmatter with exactly one
type:— one of:added,improved,fixed,changed,removed,deprecated,security. - Optionally add
highlight: trueto also surface the entry in the in-app What's New reel (the animated top-right badge,W/Ctrl+K→ "What's New"). The entry still renders in its normal type section; the flag also copies it into a### Highlightsblock leading the release. Reserve it for changes a user would be glad to discover — most fragments are not highlights. - Body — 1–2 sentences, reader-first.
---
type: added
highlight: true
---
**Bold headline.** Reader-first description of what changed for the user.
Writing style
- Open with a bold 2–4 word headline, then the detail — so someone reading only the bold text gets the whole release.
- Write for the user, not the developer — lead with the outcome, in second person ("You can now…", "Sessions now…"), not "Added support for…".
- Numbers over adjectives ("~150ms instead of up to 2s", never "much faster").
code-format the concretes — keys, commands, paths (Ctrl+K,~/Documents).- One idea per bullet; ban hype words (seamless, powerful, delightful, blazing).
- Skip internal-only changes — refactors, new internal packages, docs files are not changelog-worthy on their own.
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 · 57 lines · 0 tokens per session scan A 66d816cb5b53
update-changelog is a skill published in the GitHub repository brizzai/fleet (52 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 660 tokens. 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-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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.