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 agentmods add skills/fusengine/agents/changelog-scannpx skills add fusengine/agents --skill changelog-scangit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/changelog-scan)<a href="https://agentmods.dev/skills/fusengine/agents/changelog-scan"><img src="https://agentmods.dev/badge/skills/fusengine/agents/changelog-scan.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00605 |
| Opus 5 | $0.00012 | $0.00302 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
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 today.
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 — 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
- Fetch changelog via the harness CLI (ported from the old
fetch-changeloginto@fusengine/harness):bun ${CLAUDE_PLUGIN_ROOT}/../node_modules/@fusengine/harness/dist/cli/bin.mjs changelogIt fetchescode.claude.com/docs/en/changelog.md, parses versions (current MDX<Update label="X.Y.Z">format + legacy## vX.Y.Zfallback), 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. - Parse version numbers and release dates
- Extract changes per version (features, fixes, breaking)
- Compare with last known version from state file
- Generate report using templates/changelog-report.md
Version Detection
Parse patterns from changelog:
## vX.Y.Zor## X.Y.Z- Version headers### Breaking Changes- Breaking section### New Features- Features section### Bug Fixes- Fixes section
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.
- today First seen · 54 lines · 24 tokens per session scan A 2c00e4ebc589
changelog-scan is a skill published in the GitHub repository fusengine/agents (25 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 605 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
obsidian-skill
Controls Obsidian vaults via the official CLI (1.12+). Reads, creates, appends to, and searches notes. Manages daily notes, tasks, tags, properties, templates, bookmarks, and plugins. Analyzes knowledge graph structure including backlinks, orphans, and unresolved links. Triggers on Obsidian, vault, notes, daily notes…
radin-review
Run a thermo-nuclear code quality review over a scope (commit, PR, directory, or a range like "since yesterday") and log each finding as a backlog entry instead of printing to terminal. Use for /radin-review, "review and log to backlog", "audit this commit/PR/directory and file backlog entries", "turn this review into…
radin-doctor
Check that radin's own install under /.claude is complete and its optional companion tools are reachable. Use for /radin-doctor, "check my radin install", "is radin installed correctly", "radin doctor", "verify radin install".
radin-uninstall
Remove everything install.sh copied into /.claude -- radin's agent, skills, and lib scripts. Use for /radin-uninstall, "uninstall radin", "remove radin", "tear down radin", "get rid of radin".
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.
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.