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 noahlz/claude-plugins --skill update-changeloggit clone --depth 1 https://github.com/noahlz/claude-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/noahlz/claude-plugins/update-changelog)<a href="https://agentmods.dev/skills/noahlz/claude-plugins/update-changelog"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/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/noahlz/claude-plugins/update-changelog"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/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.00026 | $0.01312 |
| Opus 5 | $0.00013 | $0.00656 |
| Sonnet 5 | $0.00005 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade B, and why
update-changelog scanned grade B with 1 finding 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Found** → `cat .claude/settings.plugins.update-changelog.json`, extract `changelogPath` as `CHANGELOG_PATH`. Verify with `git ls-files --error-unmatch "{{CHANGELOG_PATH}}" 2>/dev/null || test -f "{{CHANGELOG_PATH}}"` How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write changelog entries for commits since the last release, matching the project's existing format.
Activate only on /update-changelog or explicit request. Follow steps EXACTLY.
Workflow Checklist
- [ ] 0. Config check
- [ ] 1. Detect latest tag
- [ ] 2. Collect commits
- [ ] 3. Read existing changelog
- [ ] 4. Filter and categorize (silent)
- [ ] 5. Present and confirm
- [ ] 6. Write changelog
SKILL_BASE_DIR: ${CLAUDE_SKILL_DIR}
⛔ If SKILL_BASE_DIR shows literal ${CLAUDE_SKILL_DIR}, halt: "This skill requires Claude Code 2.1.69 or higher."
Silence: Narrate only STEP_DESCRIPTION steps; execute all others silently.
Format fidelity: Detect and match the existing changelog's format. Never impose a new one.
Step 0 — Config Check
Run: node "${CLAUDE_SKILL_DIR}/../../lib/check-skill-config.js" "./.claude/settings.plugins.update-changelog.json"
- Found →
cat .claude/settings.plugins.update-changelog.json, extractchangelogPathasCHANGELOG_PATH. Verify withgit ls-files --error-unmatch "{{CHANGELOG_PATH}}" 2>/dev/null || test -f "{{CHANGELOG_PATH}}". If missing, ask for correct path (default:./CHANGELOG.md) and update config. - NOT_CONFIGURED → say config is missing. Ask: "Where is your changelog file? (default:
./CHANGELOG.md)" Store asCHANGELOG_PATH. Write:echo '{"changelogPath":"{{CHANGELOG_PATH}}"}' > .claude/settings.plugins.update-changelog.json
Step 1 — Detect Latest Tag
STEP_DESCRIPTION: "Detecting latest release tag"
Run: git tag --list --sort=-v:refname
Find the most recent semver-like tag (v1.2.3, 1.2.3, release-1.2.3, or any digits-and-dots pattern). Store as LATEST_TAG; strip prefix for LATEST_VERSION.
No semver tag → say so and HALT.
Step 2 — Collect Commits
STEP_DESCRIPTION: "Collecting commits since last release"
Run: git log {{LATEST_TAG}}..HEAD --pretty=format:"%h|%s|%b---END---"
Empty output → say "No changes since {{LATEST_TAG}}." and HALT.
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.
- 9d ago First seen · 133 lines · 26 tokens per session scan B 37fc4c3825c8
update-changelog is a skill published in the GitHub repository noahlz/claude-plugins (5 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 1,312 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.