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 check-claude-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/check-claude-changelog)<a href="https://agentmods.dev/skills/noahlz/claude-plugins/check-claude-changelog"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/check-claude-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/check-claude-changelog"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/check-claude-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.00032 | $0.01087 |
| Opus 5 | $0.00016 | $0.00544 |
| Sonnet 5 | $0.00006 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade B, and why
check-claude-changelog scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. `~/.claude/settings.json` — user-level settings and hooks Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash(curl *) How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check for Claude Code updates relevant to the current project.
Activate only on /check-claude-changelog or explicit request about Claude Code updates.
Arguments
Optional: since <version> — show changes since a specific version (e.g. /check-claude-changelog since 2.1.50).
When no argument is provided, defaults to showing changes since the last git commit date.
Skill Context
SKILL_BASE_DIR: ${CLAUDE_SKILL_DIR}
VERSION CHECK: If SKILL_BASE_DIR above shows literal ${CLAUDE_SKILL_DIR} instead of a real path, halt: "This skill requires Claude Code 2.1.69 or higher."
Node.js Check: !node "${CLAUDE_SKILL_DIR}/../../lib/check-node-version.js"
HALT if Node.js Check shows ERROR.
Rules
| Rule | Behavior |
|---|---|
| DELEGATE_TO | Read the referenced file, execute its instructions, return here. |
| Narration | Narrate only STEP_DESCRIPTION steps; all others silent. |
| Script output | Scripts return JSON: status ("success" or "error"), data or message. |
Workflow
0. Parse Arguments
If since <version> argument found (must match \d+\.\d+\.\d+): set sinceVersion, skip Step 1, proceed to Step 2.
Otherwise: proceed to Step 1.
1. Get Last Commit Date
STEP_DESCRIPTION: "Checking last commit date"
Run: git log -1 --format="%aI %h %s" HEAD
If the repo has commits: note the ISO date, short date, short SHA, and subject.
If no commits: default to 30 days ago. Note "No commits found — showing recent versions."
2. Fetch Changelog
STEP_DESCRIPTION: "Fetching Claude Code changelog"
If sinceVersion is set:
node "${CLAUDE_SKILL_DIR}/scripts/fetch-changelog.js" --since-version "{{sinceVersion}}"
Otherwise:
node "${CLAUDE_SKILL_DIR}/scripts/fetch-changelog.js" --since "{{last_commit_date}}"
On success: the script writes the full changelog to a temp file. Use the Read tool on the changelogFile path from the JSON output to get the content. DO NOT fetch the changelog again — use this file for all subsequent steps.
What ships with it
4 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 · 145 lines · 32 tokens per session scan B 92c1b2c4f475
check-claude-changelog is a skill published in the GitHub repository noahlz/claude-plugins (5 stars, last pushed 9d ago), licensed MIT. It adds 32 tokens to every session and 1,087 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). 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.