Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/d-oit/rust-2026-templatenpx agentmods add commands/d-oit/rust-2026-template/bump-template-versionWrote 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/bump-template-version)<a href="https://agentmods.dev/commands/d-oit/rust-2026-template/bump-template-version"><img src="https://agentmods.dev/badge/commands/d-oit/rust-2026-template/bump-template-version/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/d-oit/rust-2026-template/bump-template-version"><img src="https://agentmods.dev/badge/commands/d-oit/rust-2026-template/bump-template-version.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.00000 | $0.00961 |
| Opus 5.5 | $0.00000 | $0.00384 |
| Sonnet 5.5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
bump-template-version 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 1mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: bump-template-version
Description
Bumps the template repository's own internal version — the version tracked
in .template/CHANGELOG-TEMPLATE.md's link footer. This is the SOLE place
where the template's version lives, by design — VERSION, CHANGELOG.md,
Cargo.toml [workspace.package].version, and the README.md version badge are
all kept free of any version number so a bump-template-version run mutates
exactly one file.
The per-repo version that derived repos use (in their own VERSION /
Cargo.toml [workspace.package].version / CHANGELOG.md) starts at 0.0.0
(the init value they inherit) and is bumped separately by
scripts/bump-version.sh after a repo is initialized via init-template.sh.
When to use
After merging a batch of template improvements (CI/workflow fixes, new badges, new scripts, skill additions) and you're ready to publish the next template version. Typical cadence: few times per month, not per-PR.
Execution Protocol
-
Pre-flight (required):
- Ensure
.template/CHANGELOG-TEMPLATE.mdhas a populated## [Unreleased]section with the changes you want to publish. - Confirm
VERSION,CHANGELOG.md, andCargo.toml [workspace.package].versionare still in their initial (untouched) state (VERSION=0.0.0, the generated-project starter version;CHANGELOG.md= empty Keep-a-Changelog skeleton). The script will refuse to touch them, but verify as a sanity check.
- Ensure
-
Dry run (always do this first):
bash scripts/bump-template-version.shDefault: auto-increments the PATCH component of the current version. Prints exactly which lines in
.template/CHANGELOG-TEMPLATE.mdwould change without modifying anything. -
Apply:
bash scripts/bump-template-version.sh --executeOptional flags:
--minor,--majorto bump a non-patch component.--version=X.Y.Zto set an explicit version (skips auto-increment).--date=YYYY-MM-DDto override today's date in the changelog.
-
Review and commit:
git diff .template/CHANGELOG-TEMPLATE.md(should be exactly ONE file)git add .template/CHANGELOG-TEMPLATE.mdgit commit -m 'chore(template): bump version to X.Y.Z'
-
Tag and push:
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.
- 1mo ago First seen · 81 lines · 0 tokens per session scan A 1c3b0cedf10b
bump-template-version is a command published in the GitHub repository d-oit/rust-2026-template (14 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 961 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-08-31.
Other commands, from other repositories
cargo-publish
Command "cargo-publish" from olorehq/olore, covering cargo-publish(1), name, synopsis, description and options.
recover
Scan orphaned worktrees and stale branches, then offer explicit approval-gated cleanup.
prepare-release
Release readiness review with project-steward (commits, version sync, changelog, updater).
end
End a session — log what happened, update state and the decision log, propose memory updates, and check for uncommitted or unpushed work.
create-pr
Create a GitHub pull request from a pushed branch with ticket-aware title and body generation. Not for: committing, pushing, merging, releasing, or editing an existing PR. Output: a dry-run gh pr create command by default, or the created PR URL after explicit execution.
create-release
Cuts a new release of a software project or plugin, coordinating release configuration, version files, changelog, validation, and the fixed git/PR/tag/CI sequence. Not for: PHP package publication or ordinary commits. Output: a validated release preparation or publication result with the human merge gate preserved.