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/travisjneuman/.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/travisjneuman/.claude/changelog)<a href="https://agentmods.dev/commands/travisjneuman/.claude/changelog"><img src="https://agentmods.dev/badge/commands/travisjneuman/.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/travisjneuman/.claude/changelog"><img src="https://agentmods.dev/badge/commands/travisjneuman/.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.00016 | $0.01005 |
| Opus 5 | $0.00008 | $0.00502 |
| Sonnet 5 | $0.00003 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
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 8d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator
Generates a formatted changelog entry by analyzing git commits since the last tag, grouped by conventional commit type.
Usage
/changelog [version]
Execution Protocol
Step 1: Find Latest Tag
git describe --tags --abbrev=0 2>/dev/null || echo "NO_TAG"
If no tags exist, collect all commits on the current branch.
Report the tag found and its date.
Step 2: Collect Commits Since Tag
# All commits since the latest tag (one-line format with hash)
git log <latest-tag>..HEAD --oneline --no-merges
If no tag exists:
git log --oneline --no-merges -50
Report total commit count found.
Step 3: Classify Commits by Type
Parse each commit message for conventional commit prefixes. Group into these categories:
| Prefix | Section Header | Description |
|---|---|---|
feat: |
Added | New features |
fix: |
Fixed | Bug fixes |
docs: |
Documentation | Documentation changes |
chore: |
Maintenance | Chores, dependency updates |
refactor: |
Changed | Refactors without behavior change |
perf: |
Performance | Performance improvements |
test: |
Tests | Test additions or changes |
style: |
Style | Code style, formatting |
ci: |
CI/CD | Pipeline and CI changes |
build: |
Build | Build system changes |
| (no prefix) | Other | Commits without conventional prefix |
For each commit:
- Strip the type prefix and optional scope
(scope):from the message - Capitalize the first letter of the remaining message
- Include the short hash as a reference
Step 4: Determine Version
If {{version}} is provided, use it directly.
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.
- 8d ago First seen · 169 lines · 16 tokens per session scan A 4132a85d01ff
changelog is a command published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 1,005 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-09-03.
Other commands, from other repositories
versioning
Universal version file discovery and sync. Works with any project structure.
ship-csk
DoD gate + commit proposal (waits for approval).
doc-changelog
Generation and maintenance of the project changelog.
commit-message
Generate a conventional commit message from staged changes.
pr-description
Generate a PR title and description from the current branch diff against main.
ops-gitflow
Manage the GitFlow branching model: init, feature, release and hotfix branches.