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 skills add xonovex/platform --skill versioning-guidegit clone --depth 1 https://github.com/xonovex/platformWrote 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/xonovex/platform/versioning-guide)<a href="https://agentmods.dev/skills/xonovex/platform/versioning-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/versioning-guide/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/skills/xonovex/platform/versioning-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/versioning-guide.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.00091 | $0.00688 |
| Opus 5.5 | $0.00036 | $0.00275 |
| Sonnet 5.5 | $0.00018 | $0.00138 |
| Haiku 4.5 | $0.00009 | $0.00069 |
Grade A, and why
versioning-guide 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Versioning Guidelines
Bump versions, propagate them across a workspace, and record changelogs: following Semantic Versioning and Conventional Commits.
Core Principles
- Semantic Versioning: bump MAJOR/MINOR/PATCH by the change's compatibility and reset the lower fields; a pre-release sorts below its release, see references/semver.md
- Range-preserving propagation: when the new version falls outside a dependent's range, rewrite that range in place keeping
^/~/workspace:and patch-bump the unbumped non-private dependent, transitively; an in-range dependent stays untouched unless an always-bump policy is explicit, see references/version-bump.md - Idempotent bumps: skip a package that is already bumped, keying the signal on the right baseline (committed diff before commit, registry/tag after), see references/version-bump.md
- Changelog from intent, newest-first: prepend a leveled entry; never paste raw git logs, see references/changelog.md
Operations
- version-bump: compute the next version, propagate to workspace dependents, write a changelog entry, see references/version-bump.md
- version-detect: list packages whose version changed between two git refs, see references/version-detect.md
Gotchas
- Overwriting a dependent's
^1.2.0with a bare1.3.0strips the caret and theworkspace:protocol: splice the version into the range, keep the operator - Git-diff idempotency silently re-bumps once the previous bump is committed: change the "already done" signal after commit
- Propagating only to direct dependents leaves transitive dependents with stale ranges: recurse or re-run in topological order
\w/\d+regexes mis-validate versions (they allow_and leading zeroes and reject valid multi-field pre-releases): match the real grammar or use a semver library
What ships with it
8 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.
- 1mo ago First seen · 35 lines · 91 tokens per session scan A 355b795d72ab
versioning-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 4d ago), licensed MIT. It adds 91 tokens to every session and 688 once invoked, about $0.0004 per session on Opus 5.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-08.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
create-release
Create a versioned GitHub release with changelog.
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.