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 commands/guess/claude_code/update-changeloggit clone --depth 1 https://github.com/guess/claude_codeWhat 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.00009 | $0.01295 |
| Opus 5 | $0.00005 | $0.00647 |
| Sonnet 5 | $0.00002 | $0.00259 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
update-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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Changelog
This command automatically updates the CHANGELOG.md file by analyzing git commits since the last changelog update.
Usage
/update-changelog
Description
This command will:
- Check if a CHANGELOG.md file exists
- If not found, create one with the standard Keep a Changelog header
- Find the last commit referenced in the changelog (or start from the beginning if none)
- Fetch all commits since that reference
- Parse each commit message to extract:
- The gitmoji and/or conventional commit type (feat, fix, chore, etc.)
- The commit description
- The commit hash (short form)
- Filter commits to include ONLY user-facing changes (see filtering rules below)
- Group commits by type into changelog sections:
- ✨ feat → Added
- 🐛 fix, 🚑️ hotfix → Fixed
- ♻️ refactor, 🎨 style → Changed
- 🗑️ deprecate → Deprecated
- 🔥 remove → Removed
- 🔒️ security → Security
- All other types → Other Changes
- Add entries to the "Unreleased" section at the top of the changelog
- Format entries as:
- Description ([commit-hash])
What to Include vs Exclude
IMPORTANT: The changelog is for library USERS, not developers. Only document changes that affect how users interact with or use the library.
✅ SHOULD Include
Changes that affect library users:
- New features - New public APIs, functions, modules, options
- Bug fixes - Fixes to public API behavior or user-facing issues
- Breaking changes - Changes to public APIs, function signatures, behavior
- Deprecations - Deprecated public APIs or features
- Performance improvements - User-visible performance changes
- Documentation - Updates to README, guides, or public API docs that help users
- Dependencies - Changes to runtime dependencies that users need to know about
❌ SHOULD NOT Include
Internal changes that don't affect library users:
- Internal tooling - Changes to
.claude/configs, slash commands, AI prompts - Development infrastructure - CI/CD configs, test scripts, build tools
- Internal refactoring - Code reorganization without API changes
- Development dependencies - Changes to dev/test-only dependencies
- Proposals and planning - Design docs, proposals, roadmaps in
docs/ - Internal documentation - CLAUDE.md, development notes, architecture docs for contributors
- Code style/formatting - Formatting changes, linting fixes without functional changes
- Test code - Test additions or changes (unless they reveal new features)
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.
- 3d ago First seen · 128 lines · 9 tokens per session scan A fad59e5fd5fd
update-changelog is a command published in the GitHub repository guess/claude_code (96 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 1,295 once invoked, about $0.0000 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 commands, from other repositories
setup
Interactive setup for Elixir LSP development environment.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.
commit
Based on the above changes, create a single git commit.
commit
Safe git commit practices for MindRoom.
commit
Create a Conventional Commit with signoff.