Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add selic/skills/plugin install selic-skillsWrote 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/selic/skills/release-mcp-version)<a href="https://agentmods.dev/skills/selic/skills/release-mcp-version"><img src="https://agentmods.dev/badge/skills/selic/skills/release-mcp-version.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.1 | $0.00146 | $0.01830 |
| Opus 5 | $0.00073 | $0.00915 |
| Sonnet 5 | $0.00029 | $0.00366 |
| Haiku 4.5 | $0.00015 | $0.00183 |
Grade A, and why
release-mcp-version 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 8d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release a new MCP-server version
Incremental-release runbook for a repo that already has the distribution
pipeline in place (npm package, server.json, optional manifest.json, a
tag-triggered release.yml, and — if containerised — a docker-publish.yml).
Publish-only: npm + the official MCP registry + a GitHub release. Container
redeploy is the optional appendix, not part of a normal release.
Auto-detect the target from the repo in the cwd: read package.json for name,
mcpName, and the current version.
Bundled resource: bump.mjs sits next to this file — invoke it as
node "<skill-dir>/bump.mjs" …, where <skill-dir> is wherever this skill lives
(~/.claude/skills/release-mcp-version/, or as a plugin
$CLAUDE_PLUGIN_ROOT/skills/release-mcp-version/). The lockstep/online validator
is check.mjs from the companion publish-mcp-server skill.
⚠️ Steps that need the user's explicit go-ahead
The harness will (correctly) block these; do not retry silently — pause and ask:
- Landing on
main— a direct push to the default branch, or merging a PR you authored yourself. Ask the user to confirm, or have them merge in the GitHub UI. - (Appendix only) a production container redeploy.
Everything else runs unattended, except the registry device-flow, where you surface a code + URL and the user approves in a browser.
Phase 0 — preflight
- Confirm the cwd is the intended repo (
node -p "require('./package.json').name"). - Working tree clean (
git status --short); onmainor the release branch/PR. - Green locally:
npm ci && npm run build && npm test. - Choose the semver bump from what changed: patch (fixes), minor (additive,
backward-compatible), major (breaking). On
0.x, treat breaking as a minor. - Confirm the npm token is in THIS repo's Actions secrets — it's per-repo:
gh api repos/<owner>/<repo>/actions/secrets --jq '.secrets[].name'should listNPM_TOKEN. A token in another repo does not apply and can't be copied (secrets are write-only). If missing:gh secret set NPM_TOKEN --repo <owner>/<repo>(paste at the prompt), or plan tonpm publishby hand.
What ships with it
1 file 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.
- 8d ago First seen · 138 lines · 0 tokens per session scan A 6721debc6218
release-mcp-version is a skill published in the GitHub repository selic/skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 146 tokens to every session and 1,830 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
skill-ship
Package and finalize completed work for delivery — use when a feature is done and ready to ship.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…