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 release-processgit 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/release-process)<a href="https://agentmods.dev/skills/sbroenne/mcp-server-excel/release-process"><img src="https://agentmods.dev/badge/skills/sbroenne/mcp-server-excel/release-process/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/release-process"><img src="https://agentmods.dev/badge/skills/sbroenne/mcp-server-excel/release-process.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.00019 | $0.02409 |
| Opus 5.5 | $0.00008 | $0.00964 |
| Sonnet 5.5 | $0.00004 | $0.00482 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
release-process 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Process
This is the canonical Squad release runbook. Squad has three release channels and two long-lived branches:
| Source | Version | GitHub | npm | Standalone | Homebrew/WinGet |
|---|---|---|---|---|---|
Insider dispatch from dev |
Generated X.Y.Z-insider.N |
Prerelease | insider |
Yes | Yes |
Release dispatch from dev |
X.Y.Z-preview.N |
Prerelease | preview |
Yes | Yes |
Push to main by promotion workflow |
X.Y.Z |
Stable/latest | latest |
Yes | Yes |
The repository does not use a staging preview branch. Preview is a release
channel, not a branch.
Non-negotiable rules
- Never create release tags or GitHub Releases manually.
squad-release.ymlcreates both. - Never reuse a version. A preview such as
0.14.0-preview.1and stable0.14.0are separate immutable releases. - Keep the root, SDK, and CLI versions identical.
- Set the CLI's SDK dependency floor to
>=VERSION; prerelease workspaces do not match an older stable range. - Add an exact
## [VERSION]entry toCHANGELOG.md. - Merge release preparation to
devand wait for CI before dispatching. - Keep separate Homebrew casks and WinGet identifiers for each channel.
Required credentials
Configure these GitHub Actions secrets:
NPM_TOKEN: an automation-capable npm publish token that does not require an interactive OTP.HOMEBREW_TAP_TOKEN: a classic GitHub PAT withpublic_repo, owned by an account that has write access tobradygaster/homebrew-squad.WINGET_CREATE_GITHUB_TOKEN: a classic GitHub PAT withpublic_repo, owned by the account that maintainstamirdresher/winget-pkgs.
Human release-trigger boundary
Agents may prepare versions, run validation, and recommend exact commands, but
agents must never execute or dispatch live publication, promotion, or recovery
workflows. Only a human executes the real trigger for these live workflows:
squad-release.yml, squad-agents-ai-release.yml, squad-insider-publish.yml,
squad-promote.yml with dry_run=false, squad-version-promote.yml,
squad-npm-publish.yml, or squad-standalone-release.yml.
Treat squad-promote.yml --ref dev -f dry_run=true as human-only too: the
workflow still has actions: write and contents: write, checks out dev
with the workflow token, installs dependencies, and runs the release build and
tests. Do not describe any GitHub Actions release workflow as agent-safe once
it has write-capable credentials or a dispatch path. Stop with verified
commands and evidence for a human to run; human approval alone does not
authorize an agent to fire the trigger.
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 · 270 lines · 19 tokens per session scan A 1afe797d4f2d
release-process is a skill published in the GitHub repository sbroenne/mcp-server-excel (817 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 2,409 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…