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 sbroenne/mcp-server-excel --skill versioning-policygit clone --depth 1 https://github.com/sbroenne/mcp-server-excelWrote 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/sbroenne/mcp-server-excel/versioning-policy)<a href="https://agentmods.dev/skills/sbroenne/mcp-server-excel/versioning-policy"><img src="https://agentmods.dev/badge/skills/sbroenne/mcp-server-excel/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/sbroenne/mcp-server-excel/versioning-policy"><img src="https://agentmods.dev/badge/skills/sbroenne/mcp-server-excel/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.01153 |
| Opus 5.5 | $0.00008 | $0.00461 |
| Sonnet 5.5 | $0.00004 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00115 |
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 7d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Squad publishes @bradygaster/squad-sdk and
@bradygaster/squad-cli from one npm workspace. Their versions and the root
version move together. A mismatched prerelease dependency can make npm silently
resolve an older registry SDK instead of the local workspace.
1. Supported versions
| Use | Version | Committed branch |
|---|---|---|
| Stable release | MAJOR.MINOR.PATCH |
main, and briefly dev during promotion |
| Preview release | MAJOR.MINOR.PATCH-preview.N |
dev |
| Insider snapshot | MAJOR.MINOR.PATCH-insider.N |
Generated by the insider workflow |
| Local build | MAJOR.MINOR.PATCH-build.N |
Never committed |
preview is a release channel, not a branch. Stable promotion merges a
sanitized release tree directly from dev to main.
2. Package versions stay in lockstep
These versions must always be identical:
package.jsonpackages/squad-sdk/package.jsonpackages/squad-cli/package.json- the corresponding workspace entries in
package-lock.json
Use the workspace-aware version command:
npm version "$VERSION" --workspaces --include-workspace-root --no-git-tag-version
Never edit only one package version.
3. Prerelease workspace dependency rule
The CLI depends on the SDK through a SemVer range. SemVer deliberately excludes
prereleases unless the comparator names a prerelease with the same base version.
For example, >=0.13.0 does not match 0.14.0-preview.1.
For every committed preview version, set both the CLI manifest and lockfile dependency floor to that exact preview:
npm pkg set "dependencies.@bradygaster/squad-sdk=>=$VERSION" \
--workspace @bradygaster/squad-cli
npm install --package-lock-only
For VERSION=0.14.0-preview.1, the required range is
>=0.14.0-preview.1. Before stable promotion, change the version and floor to
0.14.0 / >=0.14.0; never leave a prerelease floor in a stable release.
This rule prevents the PR #640 failure mode, where the build succeeded against a stale published SDK rather than the workspace SDK.
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.
- 7d ago First seen · 124 lines · 20 tokens per session scan A 7e35d50b1945
versioning-policy is a skill published in the GitHub repository sbroenne/mcp-server-excel (817 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,153 once invoked, about $0.0001 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-10-07.
Other skills, from other repositories
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). 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 complete — this skill is the post-wrapup…
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
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, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…