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 cyanheads/musicbrainz-mcp-server --skill release-and-publishgit clone --depth 1 https://github.com/cyanheads/musicbrainz-mcp-serverWrote 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/cyanheads/musicbrainz-mcp-server/release-and-publish)<a href="https://agentmods.dev/skills/cyanheads/musicbrainz-mcp-server/release-and-publish"><img src="https://agentmods.dev/badge/skills/cyanheads/musicbrainz-mcp-server/release-and-publish/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/cyanheads/musicbrainz-mcp-server/release-and-publish"><img src="https://agentmods.dev/badge/skills/cyanheads/musicbrainz-mcp-server/release-and-publish.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.00112 | $0.02864 |
| Opus 5 | $0.00056 | $0.01432 |
| Sonnet 5 | $0.00022 | $0.00573 |
| Haiku 4.5 | $0.00011 | $0.00286 |
Grade A, and why
release-and-publish scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **MCP Registry**: `curl -s "https://registry.modelcontextprotocol.io/v0.1/servers/<mcpName>/versions/<version>"` — must return HTTP 200 with `server.version` matching `<version>` (`mcpName` is the `name` field from `se This is a copy
92% identical to release-and-publish — 140 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preconditions
This skill runs after git wrapup. By the time it's invoked:
- Pre-wrapup verification is done (
field-test,security-pass,polish-docs-metaas applicable) package.jsonversion is bumpedchangelog/<major.minor>.x/<version>.mdis authoredCHANGELOG.mdis regenerated- README and every version-bearing file is in sync
- Release commit (
chore: release v<version>) exists - Annotated tag (
v<version>) exists locally - Working tree is clean
If any are missing, halt and tell the user to finish wrapup first. Do not attempt to redo wrapup work from inside this skill.
Failure Protocol
Steps 3–7 are network-bound. For those, retry transient failures up to 2 times with short backoff (~5 s before the first retry, ~15 s before the second) before halting. All other steps halt on the first non-zero exit — they're deterministic and a second attempt won't change the outcome.
Retry on transient patterns
Match stderr (case-insensitive) against any of these — if matched, the failure is almost always a network blip; retry:
integrity check failed/IntegrityCheckFailed— corrupt tarball during downloadECONNRESET/EAI_AGAIN/ETIMEDOUT/ENOTFOUND— network layerconnection reset/connection refused— transport bliptimed out/request timeout— server or network timeout- HTTP
502/503/504— transient registry error
Before retrying docker buildx --push (step 7), run docker builder prune -f to drop any cached corrupt layer. Skip this extra step for other retries.
Never retry on idempotent-success signals
These mean the step already succeeded on a prior run — treat as success and proceed to the next step:
- npm (
bun publish):version already exists,You cannot publish over the previously published versions - MCP Registry (
mcp-publisher publish):cannot publish duplicate version - GitHub Release (
gh release create):release already exists— fall back togh release upload --clobber(see step 6)
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.
- 12d ago First seen · 222 lines · 112 tokens per session scan A 957109bba580
release-and-publish is a skill published in the GitHub repository cyanheads/musicbrainz-mcp-server (1 stars, last pushed 21d ago), licensed Apache-2.0. It adds 112 tokens to every session and 2,864 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 92% identical to release-and-publish, differing in 140 lines, and is treated as a copy.
Other skills, from other repositories
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
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…
release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog, decide if a change is a…
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
safe-deployment
Discipline for shipping changes reversibly, decouple deploy (code reaches production) from release (users see it) with feature flags, roll out progressively, and define the automated rollback trigger before shipping, not during the incident. Use when the user asks how to deploy a risky change, choose between…