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 slbug/claude-ruby-grape-rails --skill cc-changeloggit clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWrote 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/slbug/claude-ruby-grape-rails/cc-changelog)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/cc-changelog"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/cc-changelog.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.1 | $0.00050 | $0.00839 |
| Opus 5 | $0.00025 | $0.00419 |
| Sonnet 5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
cc-changelog 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Changelog Assistant
Audience: Agents, Not Humans
Imperative-only. Tables for category and shape lists.
Usage
| Command | Purpose |
|---|---|
/cc-changelog |
check for new CC versions, analyze impact |
/cc-changelog --all |
re-analyze all versions (ignore last check) |
/cc-changelog --set=<version> |
reset last checked version, then re-run |
Execution Flow
Step 1: Fetch New Entries
From repo root: bash ./scripts/fetch-cc-changelog.sh (or --all for full re-fetch).
| Output prefix | Action |
|---|---|
STATUS: UP_TO_DATE |
report "No new CC versions" and stop |
STATUS: NEW_VERSIONS |
continue with content below the header |
--all flag → bash ./scripts/fetch-cc-changelog.sh --all.
--set=X flag → bash ./scripts/fetch-cc-changelog.sh --set=X, then re-run without flag.
Step 2: Analyze Impact
Read new changelog entries. Classify each into one category:
| Category | Meaning | Action |
|---|---|---|
| BREAKING | may break existing plugin functionality | immediate fix required |
| OPPORTUNITY | new CC feature plugin could use | add to backlog/plan |
| RELEVANT FIX | CC fixed a bug we worked around | check if workaround removable |
| DEPRECATION | CC removing something we use | plan migration |
| INFO | good to know, no action needed | log only |
Cross-reference plugin components via ${CLAUDE_SKILL_DIR}/references/analysis-rules.md.
Step 3: Generate Report
Output structured report:
## CC Changelog Analysis: v{last_checked} → v{latest}
### BREAKING (action required)
- [version] description → **Impact**: which plugin file/component
**Fix**: specific action needed
### OPPORTUNITY (new features)
- [version] description → **Use case**: how plugin could benefit
**Files**: which plugin files to update
### RELEVANT FIX (workaround removal)
- [version] description → **Current workaround**: what we do now
**Action**: can we simplify?
### DEPRECATION (migration needed)
- [version] description → **We use this in**: file:line
**Migration**: what to change
### INFO (no action)
- [version] brief summary (collapsed)
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.
- 7d ago First seen · 105 lines · 50 tokens per session scan A 98df92c11114
cc-changelog is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 839 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.
finalize
Finalize orphaned recordings - stop processes, compress, push to orphan branch. TRIGGERS - finalize recording, stop asciinema, orphaned recording.
github
Use when automating GitHub issues, pull requests, reviews, CI checks, labels, releases, or engineering collaboration loops through the GitHub CLI.