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 skills/d-o-hub/github-template-ai-agents/template-version-managementnpx skills add d-o-hub/github-template-ai-agents --skill template-version-managementgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/skills/d-o-hub/github-template-ai-agents/template-version-management)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/template-version-management"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/template-version-management.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.00131 | $0.02049 |
| Opus 5 | $0.00066 | $0.01025 |
| Sonnet 5 | $0.00026 | $0.00410 |
| Haiku 4.5 | $0.00013 | $0.00205 |
Grade A, and why
template-version-management 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template Version Management
Versioning in a template repository follows a different mental model than a regular project. VERSION is the consumer-side default (always 0.0.0); the template's own release history is canonical in .template/CHANGELOG-TEMPLATE.md; only README.md displays a template version badge; and the existing scripts (propagate-version.sh, bump_patch_version.sh) are general-purpose utilities that downstream consumers reuse unchanged.
When to Use
- Bumping the template's own release version (e.g., 0.2.10 → 0.3.0)
- Fixing a stale template version badge in
README.md,QUICKSTART.md, oragents-docs/MIGRATION.md - Adding or updating version references when introducing a new doc file
- Answering "what's the template version" / "why is VERSION 0.0.0" / "where does the template version come from"
- Reviewing PRs that touch
VERSION,.template/CHANGELOG-TEMPLATE.md, or any version badge - Onboarding contributors to the template's version flow
The Mental Model
.template/CHANGELOG-TEMPLATE.md → template release history (the canonical source)
README.md → only doc with a template version badge
VERSION → consumer-side default (0.0.0 for templates,
project version for downstream consumers)
scripts/propagate-version.sh
→ reads VERSION, propagates to README + CHANGELOG.md
→ general-purpose; works for any consumer project
scripts/bump_patch_version.sh
→ reads VERSION, appends a new entry to
.template/CHANGELOG-TEMPLATE.md, then runs propagate-version.sh
→ general-purpose; downstream consumers use it on
their own CHANGELOG.md, not .template/CHANGELOG-TEMPLATE.md
Key rule: scripts are primary. They are designed for downstream consumer codebases and must keep their VERSION-based design unchanged. The template's own version lives in .template/CHANGELOG-TEMPLATE.md; the scripts and the template version are decoupled by design.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 140 lines · 131 tokens per session scan A 174098ef287e
template-version-management is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 131 tokens to every session and 2,049 once invoked, about $0.0007 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 skills, from other repositories
push-release
Push to GitHub and optionally bump version to trigger PyPI release.
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
release
Cut an Inspector v2 release — bump the version on v2/main first, merge the milestone into main, tag origin/main with a bare x.y.z, and publish via the GitHub Release. Also covers the v1 line and what the publish jobs gate on.
release
Cut a new SlackCLI release end to end — survey commits since the last tag, recommend a SemVer bump, open the release issue, prepare the version bump and CHANGELOG promotion on a branch, open the linked PR, and after merge push the annotated tag that publishes binaries and updates the Homebrew tap. Use when asked to…