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 huzaifa525/claude-code-optimizer --skill changeloggit clone --depth 1 https://github.com/huzaifa525/claude-code-optimizerWrote 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/huzaifa525/claude-code-optimizer/changelog)<a href="https://agentmods.dev/skills/huzaifa525/claude-code-optimizer/changelog"><img src="https://agentmods.dev/badge/skills/huzaifa525/claude-code-optimizer/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.00024 | $0.00414 |
| Opus 5 | $0.00012 | $0.00207 |
| Sonnet 5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
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.
What it actually says
Generate a changelog from git history.
Steps
-
Find the last tag
git describe --tags --abbrev=0 2>/dev/null || echo "no-tags" -
Get commits since last tag
git log [last-tag]..HEAD --oneline --no-mergesIf no tags, get last 50 commits.
-
Categorize commits by prefix:
Category Prefixes Features feat:, feature:, add: Bug Fixes fix:, bugfix:, hotfix: Performance perf: Refactoring refactor: Documentation docs:, doc: Testing test:, tests: CI/CD ci:, cd:, build: Chores chore:, deps:, bump: Breaking Changes any commit with BREAKING CHANGE in body If commits don't use conventional prefixes, categorize by content.
-
Generate CHANGELOG.md entry:
## [version] - YYYY-MM-DD ### Features - Description ([commit-hash]) ### Bug Fixes - Description ([commit-hash]) ### Performance - Description ([commit-hash]) ### Breaking Changes - Description ([commit-hash]) -
If CHANGELOG.md exists, prepend the new entry at the top (after the title). If it doesn't exist, create it.
-
Show the generated changelog to the user.
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 · 63 lines · 24 tokens per session scan A 590a9a5d7f6b
changelog is a skill published in the GitHub repository huzaifa525/claude-code-optimizer (9 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 414 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-08-31.
Other skills, from other repositories
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.
source-command-update-infos-release
Update Codex releases tracking (guide + landing + version bump).
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.