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 sundegan/agent-skills --skill update-changeloggit clone --depth 1 https://github.com/sundegan/agent-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/sundegan/agent-skills/update-changelog)<a href="https://agentmods.dev/skills/sundegan/agent-skills/update-changelog"><img src="https://agentmods.dev/badge/skills/sundegan/agent-skills/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/sundegan/agent-skills/update-changelog"><img src="https://agentmods.dev/badge/skills/sundegan/agent-skills/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.00068 | $0.02615 |
| Opus 5 | $0.00034 | $0.01307 |
| Sonnet 5 | $0.00014 | $0.00523 |
| Haiku 4.5 | $0.00007 | $0.00262 |
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 11d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Changelog
Goal
Update the current repository's Chinese and English changelog files from the last published version to the current state. The changelog should cover the release as completely as practical: summarize related code changes together, but verify that every meaningful code change in the release range is either represented by a changelog entry or explicitly excluded for a clear reason.
Default to modifying changelog files in the target repository. Do not change product code while using this skill unless the user explicitly asks.
Workflow
- Determine the target repository root with
git rev-parse --show-toplevel. - Identify changelog files:
- Prefer files explicitly named by the user.
- Otherwise search for files such as
CHANGELOG.md,CHANGELOG.zh*.md,CHANGELOG.en*.md,changelog*.md,RELEASE_NOTES.md,release-notes*.md, or existing localized changelog names. - If both Chinese and English changelogs exist, update both. If one file contains both languages, preserve that layout.
- If the repository has public website changelog pages or generated/static copies of the changelog, update those too unless the project clearly generates them from source files.
- Determine the target release identity before drafting:
- Use concrete version/date values. Take them from the user when provided; otherwise infer them from version files, release scripts/branches, tags, commit/tag metadata, existing changelog headings, release notes, and the change set.
- Resolve relative dates to absolute dates. If preparing a release now and no better date evidence exists, use the current environment date. If version files still show the last release, infer the next version from change scope and project release pattern.
- Do not leave version/date blank or use placeholders when a credible inference is possible. Ask only when evidence is insufficient; otherwise apply the inferred version/date consistently across Markdown changelogs, website/static copies, visible labels, dates, and release links.
- Determine the release range:
- Use the user-provided base tag, release version, branch, or commit when present.
- Otherwise treat "last published version" as the latest reachable release tag from
HEAD, usinggit describe --tags --abbrev=0as the first candidate. - Cross-check the latest changelog version heading against Git tags. If the latest changelog heading and latest tag disagree, inspect both and choose the one that clearly represents the last published version. Ask only if the base cannot be determined safely.
- Use
HEADas the default target. Include uncommitted changes only when the user's wording includes current working state, "now", "当前", or when changelog files are being updated in an unreleased working tree.
- Collect change evidence. Prefer running
scripts/collect_changelog_context.shfrom this skill if available:
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.
- 11d ago First seen · 135 lines · 68 tokens per session scan A e3f44dd02b63
update-changelog is a skill published in the GitHub repository sundegan/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 2,615 once invoked, about $0.0003 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.