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/d-oit/rust-2026-template/update-template-changeloggit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/update-template-changelog)<a href="https://agentmods.dev/commands/d-oit/rust-2026-template/update-template-changelog"><img src="https://agentmods.dev/badge/commands/d-oit/rust-2026-template/update-template-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 | $0.00014 | $0.00590 |
| Opus 5 | $0.00007 | $0.00295 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
update-template-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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update .template/CHANGELOG-TEMPLATE.md and README.md for a new release version.
Step 1: Determine the version
If $ARGUMENTS is provided, use it as the new version (e.g. 0.4.0, 1.0.0).
Otherwise, detect the current latest version from the changelog and bump the patch number.
Step 2: Collect changes
Run this to see commits since the last documented version:
!git log --oneline
Analyze the commit messages and categorize each into Keep a Changelog sections:
| Commit prefix | Changelog section |
|---|---|
feat |
### Added |
fix |
### Fixed |
perf |
### Changed |
refactor |
### Changed |
chore (deps, ci, tooling) |
### Changed |
docs |
### Fixed |
security |
### Security |
BREAKING CHANGE or ! |
### Changed (with breaking note) |
Skip chore: update CI status and [skip ci] commits — they are noise.
Step 3: Update CHANGELOG-TEMPLATE.md
- Read the current
.template/CHANGELOG-TEMPLATE.md. - Insert a new
## [VERSION] - YYYY-MM-DDsection right after the## [Unreleased]block (after the---separator that follows Unreleased). - Add categorized entries under the appropriate
### Added,### Changed,### Fixed,### Securitysubsections.- Only include subsections that have entries.
- Use the exact format:
- \component` description.or- Description.` for each entry. - Reference files, skills, workflows, and crates where relevant.
- Update the link references at the bottom:
- Change
[Unreleased]compare URL to point from the new version. - Add a new
[VERSION]compare URL from previous version to new version.
- Change
Step 4: Update README.md
- Read
README.md. - Update the
Template Versionbadge to the new version number and anchor link.- Badge URL:
https://img.shields.io/badge/version-VERSION-blue - Link target:
.template/CHANGELOG-TEMPLATE.md#VERSIONANCHOR
- Badge URL:
Constraints
- Follow the existing changelog style exactly (Keep a Changelog format).
- Use today's date in
YYYY-MM-DDformat. - Do not modify entries in older versions.
- Keep the
[Unreleased]section as a clean template skeleton. - Do not add comments or explanatory text to the changelog — only release notes.
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 · 60 lines · 14 tokens per session scan A c25505381994
update-template-changelog is a command published in the GitHub repository d-oit/rust-2026-template (10 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 590 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-31.
Other commands, from other repositories
recover
Scan orphaned worktrees and stale branches, then offer explicit approval-gated cleanup.
review-feature
Review a KMP feature against architecture patterns and spec.
capture
Triage raw inbox notes into reviewed repository destinations without deleting their sources.
clean-ai-writing
Audit and rewrite content to remove AI writing patterns.
migrate-gemini
Inventory and migrate selected Gemini CLI workflows with dry-run review and parity checks.
speckit.agent-context.update
Proxy for speckit.agent-context.update.md.