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/melodic-software/claude-code-plugins/changelognpx skills add melodic-software/claude-code-plugins --skill changeloggit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWhat 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.00084 | $0.02276 |
| Opus 5 | $0.00042 | $0.01138 |
| Sonnet 5 | $0.00017 | $0.00455 |
| Haiku 4.5 | $0.00008 | $0.00228 |
Grade A, and why
changelog scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **`fetch`**. WebFetch + display a version (or latest, or a `v.X..v.Y` range) of `code.claude.com/docs/en/changelog.md` (raw markdown, the smaller, chrome-free channel; WebFetch truncates it and the rendered page alike, How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Variables
Arguments: $ARGUMENTS
Scope
Ingests Claude Code changelog entries and integrates them into the repo. Covers the full arc: read upstream changes → orient on repo impact → research new features → triage with user → plan edits → implement → verify → close matching issues.
Distinct from:
/claude-ops:known-issues. Tracks CC bugs/workarounds. This skill integrates CC feature changes into repo config/docs- Any release-triage automation the consumer runs (issue filing per release). This skill IMPLEMENTS changes, holistically across a release
Input modes
Three ways to provide changelog content (priority order):
- User pastes text. Skill parses inline changelog from conversation context
- Specific version.
/claude-ops:changelog apply v2.1.152fetches that version fromcode.claude.com/docs/en/changelog.md - Auto-detect latest.
/claude-ops:changelog apply(no version) automatically fetches changelog, identifies latest version, and proceeds
Version awareness
On every apply or diff invocation, compare the target version against the active terminal's CC version, captured at load:
-
Installed CC version: !
claude --version || echo "(CC version unavailable)" -
If target version > installed version: warn user. "You're applying v2.1.152 changes but running v2.1.150. Update CC first (
claude update) or changes may reference features not yet available in your session." -
If target version = installed version: proceed normally
-
If target version < installed version: fine. Catching up on older release
Applied-version tracking
No persistent tracking file. Git history IS the tracker. Commit messages cite CC versions per Conventional Commits (chore: address Claude Code v2.1.152 changelog). The status action derives applied versions via git log --grep. Avoids drift between tracker file and git state.
Action Router
Parse $ARGUMENTS to extract the action (first token) and remaining arguments.
| Action | Description | Detail |
|---|---|---|
apply |
Full pipeline: ingest → explore → research → interview → plan → implement → verify → close issues | See "Action: apply" below |
fetch |
Fetch + display changelog for version(s). Read-only | See "Action: fetch" below |
diff |
Fetch + orient on repo impact. Read-only analysis table | See "Action: diff" below |
status |
Show applied versions, open issues, pending work | See "Action: status" below |
help |
Show action table | (inline) |
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.
- 2d ago First seen · 180 lines · 84 tokens per session scan A 2b84359fea8e
changelog is a skill published in the GitHub repository melodic-software/claude-code-plugins (13 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 2,276 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
plugin-updating
Use this skill when the user asks to bump, update, or release a new version of a plugin in the Shopware AI Coding Tools marketplace — phrases like "bump test-writing to 3.8.0", "release a patch for dev-tooling", "update the plugin version". Handles synchronized version bumps across plugin.json and every SKILL.md…
release-info-writing
Use this skill when the user is completing features, deprecations, or breaking changes in the Shopware core repository that affect external developers, or when they ask to write release info, upgrade entries, release notes, release documentation, or changelog entries — phrases like "write a release info entry for my…
deep-research
Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…
error-ux
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.
adversarial-patterns
Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.
documentation-testing
Provides heuristics for identifying incomplete or broken documentation. Use when validating README setup instructions, testing onboarding flows, or auditing documentation quality. Triggers: docs, readme, onboarding, setup validation, documentation audit.