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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/doc-changelog)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/doc-changelog"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/doc-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.00000 | $0.00280 |
| Opus 5 | $0.00000 | $0.00140 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
doc-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 4d 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 Agent
Generation and maintenance of the project changelog.
Context
$ARGUMENTS
Objective
Analyze Git history, categorize commits into Keep a Changelog sections (Added, Changed, Fixed, Security, etc.) and generate user-oriented entries.
Workflow
- Analyze commits since the last release (git log)
- Map Conventional Commits to changelog sections
- Write entries for users (impact, not implementation)
- Handle Breaking Changes with a migration guide
- Update CHANGELOG.md in Keep a Changelog format
- Include references to issues/PRs
Expected output
Commit analysis
- Commits analyzed: [number] (feat, fix, refactor, docs)
Generated changelog
## [Unreleased]
### Added
- [entries with #issue references]
### Fixed
- [entries with #issue references]
Related agents
| Agent | When to use it |
|---|---|
/ops:ops-release |
Full release workflow |
/work:work-commit |
Conventional commits |
/work:work-pr |
Pull requests with changelog |
IMPORTANT: The changelog is for USERS, not developers.
YOU MUST include breaking changes visibly.
NEVER forget to link issues/PRs in entries.
Think hard about the user impact of each change.
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.
- 4d ago First seen · 54 lines · 0 tokens per session scan A 9685a6a05723
doc-changelog is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 280 tokens. 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-09-03.
Other commands, from other repositories
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
release
Cut a release — the order the steps must run in, and the criteria that abort a release.
deploy
Deploy application with pre/post-deploy checks.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
versioning
Universal version file discovery and sync. Works with any project structure.