Borrowing it
Nothing to install: this file belongs to jens-duttke/usage-monitor-for-claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jens-duttke/usage-monitor-for-claude/main/.claude/commands/changelog.mdgit clone --depth 1 https://github.com/jens-duttke/usage-monitor-for-claudeWrote 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/commands/jens-duttke/usage-monitor-for-claude/changelog)<a href="https://agentmods.dev/commands/jens-duttke/usage-monitor-for-claude/changelog"><img src="https://agentmods.dev/badge/commands/jens-duttke/usage-monitor-for-claude/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/commands/jens-duttke/usage-monitor-for-claude/changelog"><img src="https://agentmods.dev/badge/commands/jens-duttke/usage-monitor-for-claude/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.00014 | $0.00460 |
| Opus 5 | $0.00007 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 12d 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
Add the correct CHANGELOG.md entry (or entries) for the changes in this conversation. The decision rule for whether a change deserves an entry lives in CLAUDE.md - this command is the procedure for writing the entry once you know it belongs.
Step 1: Decide whether an entry is warranted
- User-facing changes (new features, bug fixes, behavior changes, UI changes) get an entry.
- Internal refactors, code style changes, and documentation-only changes do not - unless they affect the user.
- Changes to
CLAUDE.mdand the command files are invisible to users - never mention them.
If nothing user-facing changed, say so and stop.
Step 2: For a fix, verify the bug shipped
Entries describe changes relative to the latest release tag, not intermediate commits.
- Before writing a fix entry, run
git log(and compare against the latestvX.Y.Ztag) to confirm the bug existed in the latest release. - If the bug was introduced and fixed within the current unreleased period, it gets no entry - the user never saw it.
Step 3: Write the entry
- Add it under the
## [Unreleased]section, grouped by: Added, Changed, Fixed, Removed (create the subheading only if it does not exist yet). - Write from the user's perspective - what changed and why it matters, not how the code changed.
- One bullet per logical change; keep it to a single concise sentence.
- When a change implements a GitHub Discussion or resolves a GitHub Issue, link it in the entry text, e.g.
- [Feature name](https://github.com/jens-duttke/usage-monitor-for-claude/discussions/12) - description
Step 4: Confirm
Show the added entry (or entries) and which group each landed in. Do not commit - suggest /commit-message when ready.
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.
- 12d ago First seen · 34 lines · 14 tokens per session scan A e6015967fd3b
changelog is a command published in the GitHub repository jens-duttke/usage-monitor-for-claude (282 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 460 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-30.
Other commands, from other repositories
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.
pull
A quick command that downloads the latest commits from the main Git branch into the current project.
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.