Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/kevinzai/commander/ccc-changelog)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-changelog"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-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.00038 | $0.00640 |
| Opus 5 | $0.00019 | $0.00320 |
| Sonnet 5 | $0.00008 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
ccc-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 8d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-changelog — What's New
Reads CHANGELOG.md at the repo root and surfaces the most-recent version section in a scan-friendly summary. Works whether invoked directly or triggered by the SessionStart version-transition nudge.
Steps (always in this order)
1. Locate CHANGELOG.md
Read ${CLAUDE_PLUGIN_ROOT}/../../CHANGELOG.md via the Read tool.
If that fails, try Bash: find ~ -name CHANGELOG.md -path "*/cc-commander/*" 2>/dev/null | head -1 and read the result.
If no CHANGELOG.md is found: output a friendly message — "CHANGELOG.md not found. Visit https://commanderplugin.com for release notes." and exit.
2. Extract the most-recent version section
Parse the file to find the first ## [ header (e.g. ## [4.0.0-beta.11] — 2026-04-23 — ...). Extract everything from that line up to (but not including) the next ## [ header. That is the "current release block".
If an argument (version string) was passed, instead find the section whose header contains that version string.
3. Render a digestible summary
Output in this exact structure:
## CC Commander [VERSION] — [DATE]
**[HEADLINE from changelog section if present, else first sentence of first paragraph]**
[CHANGES — grouped by emoji category, max 5 bullets per category, ≤15 words each]
---
Full notes: CHANGELOG.md
Grouping rules:
- Scan the block for sub-headers (e.g.
### Security,### Tests,### UX,### New skills) — preserve those as bold labels. - Under each label, output at most 5 bullet points, each compressed to the single most important fact.
- If a section has more than 5 items, append:
…and N more — see CHANGELOG.md. - Skip sections with zero bullets after filtering.
- Maximum total output: 30 lines (not counting the header).
4. Footer
Always end with:
Run `/ccc` to get started or `$ccc-browse` to explore all 48 skills.
Anti-patterns
- Never dump the raw CHANGELOG.md — always summarize.
- Never truncate mid-sentence — compress, don't cut.
- No numbered lists — bullets only.
- No "Let me know if..." sign-offs.
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.
- 8d ago First seen · 72 lines · 38 tokens per session scan A ebe3ee834db6
ccc-changelog is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 640 once invoked, about $0.0002 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
git-flow
Use when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional commits, short-lived branches, worktree isolation, and final merge/cleanup.
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.