changelog-scan

changelog-scan is a skill for Claude Code from fusengine/agents. It costs 24 tokens per session (605 once invoked), scanned A, original, MIT.

A release-note checker that reads the official Claude Code changelog and identifies new versions and changes since the last check.

In plain words
What is it for?
Use it to track Claude Code releases, review added or removed features, and see what changed since your previous check.
Why use it?
It saves you from manually comparing release notes and missing updates that may affect your setup.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the fuse-changelog plugin — 3 skills, 1 command, 1 agent shipped together

Good fit Use it to track Claude Code releases, review added or removed features, and see what changed since your previous check.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add fusengine/agents
Claude Code
/plugin install fuse-changelog

Made for: Claude Code.

Or install fuse-changelog, the plugin that ships this one along with the rest of its 3 skills, 1 command, 1 agent.

Wrote 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.

agentmods badge for changelog-scan

README.md
[![agentmods](https://agentmods.dev/badge/skills/fusengine/agents/changelog-scan/github.svg)](https://agentmods.dev/skills/fusengine/agents/changelog-scan)
Your own site
<a href="https://agentmods.dev/skills/fusengine/agents/changelog-scan"><img src="https://agentmods.dev/badge/skills/fusengine/agents/changelog-scan/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.

agentmods 80×15 button for changelog-scan

Your own site · 80×15
<a href="https://agentmods.dev/skills/fusengine/agents/changelog-scan"><img src="https://agentmods.dev/badge/skills/fusengine/agents/changelog-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 605 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00605
Opus 5.5 $0.00010 $0.00242
Sonnet 5.5 $0.00005 $0.00121
Haiku 4.5 $0.00002 $0.00060

Measured 1mo ago against content hash 2c00e4ebc589, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

changelog-scan 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 1mo 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.

plugins/changelog-watcher/skills/changelog-scan/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Changelog Scan Skill

Overview

Fetches and analyzes the official Claude Code changelog to detect new versions and changes.

Data Sources

Source URL Method
Changelog code.claude.com/docs/en/changelog.md WebFetch
Docs Index code.claude.com/docs/llms.txt WebFetch
Hooks Ref code.claude.com/docs/en/hooks.md WebFetch
Plugins Ref code.claude.com/docs/en/plugins-reference.md WebFetch
CLI Ref code.claude.com/docs/en/cli-reference.md WebFetch

Workflow

  1. Fetch changelog via the harness CLI (ported from the old fetch-changelog into @fusengine/harness): bun ${CLAUDE_PLUGIN_ROOT}/../node_modules/@fusengine/harness/dist/cli/bin.mjs changelog It fetches code.claude.com/docs/en/changelog.md, parses versions (current MDX <Update label="X.Y.Z"> format + legacy ## vX.Y.Z fallback), writes state to ~/.claude/logs/00-changelog/<date>-state.json, and prints JSON {latest, new_since_last_check, recent_versions}. WebFetch on the same URL is the manual fallback.
  2. Parse version numbers and release dates
  3. Extract changes per version (features, fixes, breaking)
  4. Compare with last known version from state file
  5. Generate report using templates/changelog-report.md

Version Detection

Parse patterns from changelog:

  • ## vX.Y.Z or ## X.Y.Z - Version headers
  • ### Breaking Changes - Breaking section
  • ### New Features - Features section
  • ### Bug Fixes - Fixes section

Read the full file on GitHub · 54 lines

Files

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.

Changes

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.

  1. 1mo ago First seen · 54 lines · 24 tokens per session scan A 2c00e4ebc589

Subscribe to this mod's changes

changelog-scan is a skill published in the GitHub repository fusengine/agents (33 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 605 once invoked, about $0.0001 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-03.

Related

Other skills, from other repositories

radin-record

Log bugs, follow-ups, ideas or feedback raised this session as backlog entries that outlive the conversation. Use for /radin-record or any ask to save something for later, even a vague one ("add the findings"): scan the whole session.

shortcuts/radin · 57 tokens

radin-stats

Show the stats/gain output of every companion tool that ships one, side by side.

shortcuts/radin · 24 tokens

designing-interfaces

Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or extracting patterns from existing code.

isvlasov/rageatc-oss · 39 tokens

orchestrating-software-dev

Runs software development projects from idea to completion. Use when starting a software project, adding a feature, fixing a bug, or resuming an in-progress build.

isvlasov/rageatc-oss · 39 tokens

managing-product

Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.

isvlasov/rageatc-oss · 52 tokens

enriching-roadmap

Enriches implementation roadmap chunks with acceptance criteria, pattern references, and contextual notes. Use after decomposing-work has produced the structural roadmap and before planning-software creates the orchestration plan. Does not modify chunk structure or dependencies.

isvlasov/rageatc-oss · 52 tokens