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 Azure-Samples/eShopLite --skill versioning-policygit clone --depth 1 https://github.com/Azure-Samples/eShopLiteWrote 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/azure-samples/eshoplite/versioning-policy)<a href="https://agentmods.dev/skills/azure-samples/eshoplite/versioning-policy"><img src="https://agentmods.dev/badge/skills/azure-samples/eshoplite/versioning-policy/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/azure-samples/eshoplite/versioning-policy"><img src="https://agentmods.dev/badge/skills/azure-samples/eshoplite/versioning-policy.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.00020 | $0.01506 |
| Opus 5.5 | $0.00008 | $0.00602 |
| Sonnet 5.5 | $0.00004 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
versioning-policy 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.
This is a copy
100% identical to versioning-policy — 238 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Squad is a monorepo with two publishable npm packages (@bradygaster/squad-sdk and @bradygaster/squad-cli) managed via npm workspaces. Version mismatches and prerelease leaks have caused production incidents — most notably PR #640, where a -build.N prerelease version silently broke workspace dependency resolution.
This skill codifies the versioning rules every agent must follow.
1. Version Format
All packages use strict semver: MAJOR.MINOR.PATCH
- ✅
0.9.1,1.0.0,0.10.0 - ❌
0.9.1-build.4,0.9.1-preview.1,0.8.6.1-preview
No prerelease suffixes on dev or main branches — ever.
2. Prerelease Versions Are Ephemeral
The scripts/bump-build.mjs script creates -build.N versions (e.g., 0.9.1-build.4) for local development testing only.
Rules:
-build.Nversions are created automatically during localnpm run build- They are never committed to
devormain - The script skips itself in CI (
CI=trueorSKIP_BUILD_BUMP=1) - If you see a
-build.Nversion in a PR diff, it is a bug — reject the PR
3. SDK and CLI Version Sync
Both @bradygaster/squad-sdk and @bradygaster/squad-cli MUST have the same version at all times. The root package.json version must also match.
bump-build.mjs enforces this by updating all three package.json files in lockstep (root + packages/squad-sdk + packages/squad-cli).
If versions diverge, workspace resolution silently breaks (see §4).
4. npm Workspace Semver Footgun
The CLI depends on the SDK via a workspace dependency with a semver range:
"@bradygaster/squad-sdk": ">=0.9.0"
Critical: Per the semver specification, >=0.9.0 does NOT match 0.9.1-build.4.
Semver prerelease versions (anything with a - suffix) are only matched by ranges that explicitly reference the same MAJOR.MINOR.PATCH base with a prerelease comparator. A bare >=0.9.0 range skips all prerelease versions.
What happens: When the local SDK has version 0.9.1-build.4, npm's workspace resolution fails to match the >=0.9.0 range. npm then silently installs a stale published version from the npm registry instead of using the local workspace link. The build succeeds but runs against old SDK code.
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 · 120 lines · 20 tokens per session scan A a70698d1ba0c
versioning-policy is a skill published in the GitHub repository Azure-Samples/eShopLite (168 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 1,506 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to versioning-policy, differing in 238 lines, and is treated as a copy.
Other skills, from other repositories
multi-repo-release
Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.
deploy-checklist
Generate deployment checklist for a feature before merge. Use after PR is approved, before merge, or when the user says "deploy checklist", "checklist deploy", "pre-deploy", "ready to merge?", "checklist de deploy", "posso mergear?", "pronto pra deploy?", "can I merge?", "deploy readiness". Do NOT use for CI pipeline…
agent-brain-release
Automates the release process for Agent Brain packages, including version bumping, changelog generation, git tagging, and GitHub release creation.
gsd-ship
Create PR, run review, and prepare for merge after verification passes.
dotnet-mcaf-source-control
Apply MCAF source-control guidance for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. Use when bootstrapping a repo, tightening PR flow, or documenting branch and release policy.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.