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 MuhammadUsmanGM/claude-code-best-practices --skill changeloggit clone --depth 1 https://github.com/MuhammadUsmanGM/claude-code-best-practicesWrote 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/muhammadusmangm/claude-code-best-practices/changelog)<a href="https://agentmods.dev/skills/muhammadusmangm/claude-code-best-practices/changelog"><img src="https://agentmods.dev/badge/skills/muhammadusmangm/claude-code-best-practices/changelog/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/muhammadusmangm/claude-code-best-practices/changelog"><img src="https://agentmods.dev/badge/skills/muhammadusmangm/claude-code-best-practices/changelog.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.00411 |
| Opus 5 | $0.00023 | $0.00205 |
| Sonnet 5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00005 | $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 9d 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
Changelog
Produce or update CHANGELOG.md in the Keep-a-Changelog format.
Steps
git describe --tags --abbrev=0to find the most recent tag. If no tag exists, use the repo's first commit and tell the user there's no prior tag.git log <last-tag>..HEAD --oneline --no-mergesto enumerate commits.- Read the existing
CHANGELOG.mdif present. Match its headings, casing, and date format. If missing, create one with the Keep-a-Changelog header. - Group commits into sections — Added, Changed, Fixed, Removed, Deprecated, Security — by inspecting subject prefixes (
feat:→ Added,fix:→ Fixed,refactor:/perf:→ Changed, etc.). Merge trivial commits into one bullet. - Ask the user for the new version number (semver). Do not guess.
- Insert a new
## [x.y.z] - YYYY-MM-DDsection above the previous release. Move "Unreleased" content in if present. - Show the diff before writing. Write only after confirmation.
Rules
- Rewrite commit subjects into user-facing language. "feat: add FOO" → "Added FOO that does X."
- Drop internal-only commits (
chore(deps), CI-only changes) unless they affect consumers. - Do not create a git tag. Do not commit. Hand the finished file back to the user.
Output
Print the new section you added, then stop.
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.
- 9d ago First seen · 30 lines · 46 tokens per session scan A 46c14bb1c242
changelog is a skill published in the GitHub repository MuhammadUsmanGM/claude-code-best-practices (79 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 411 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-30.
Other skills, from other repositories
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
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.
talk-stage2-research
Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only (skipped automatically in Concept mode). Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git…