What is release-and-publish?

A release-publishing workflow for sending a finished project version to package registries and release services. A registry is a service where developers find and download software packages.

Use it after version numbers, changelogs, commits, and tags are ready to publish packages to npm, the MCP Registry, GitHub Releases, or GHCR when applicable.

It checks that the release preparation is complete and handles publishing failures according to set rules. This reduces mistakes when the same version must be published in several places.

release-and-publish — Skill for Claude Code by cyanheads

Install

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.

Any agent

npx skills add cyanheads/workflows-mcp-server --skill release-and-publish

Clone the repo

git clone --depth 1 https://github.com/cyanheads/workflows-mcp-server

Made for: Claude Code.

Or install workflows-mcp-server, the plugin that ships this one along with the rest of its 34 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cyanheads/workflows-mcp-server/release-and-publish/github.svg)](https://agentmods.dev/skills/cyanheads/workflows-mcp-server/release-and-publish)

Your own site

<a href="https://agentmods.dev/skills/cyanheads/workflows-mcp-server/release-and-publish"><img src="https://agentmods.dev/badge/skills/cyanheads/workflows-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cyanheads/workflows-mcp-server/release-and-publish"><img src="https://agentmods.dev/badge/skills/cyanheads/workflows-mcp-server/release-and-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,392 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin 92% copy Near-identical to another mod in the catalogue.

Token cost

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.03392
Opus 5	$0.00056	$0.01696
Sonnet 5	$0.00022	$0.00678
Haiku 4.5	$0.00011	$0.00339

Measured 5d ago against content hash 82eed916fa4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 5d 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.

**Never disable the sandbox to complete a verification.** A verification `curl` — most often the MCP Registry one — can come back blocked by a sandbox network restriction while npm and GHCR pass. Do **not** set `dangerou

Origin

This is a copy

92% identical to release-and-publish — 124 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.

skills/release-and-publish/SKILL.md · 236 lines

How it starts

The opening of the file, as written. The whole thing — 236 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-meta as applicable)
package.json version is bumped
changelog/<major.minor>.x/<version>.md is authored
CHANGELOG.md is 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 download
ECONNRESET / EAI_AGAIN / ETIMEDOUT / ENOTFOUND — network layer
connection reset / connection refused — transport blip
timed 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 to gh release upload --clobber (see step 6)

Read the full file on GitHub · 236 lines

Changes

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.

5d ago Changed · +14 lines 82eed916fa4b
10d ago First seen · 222 lines · 112 tokens per session scan A 957109bba580

Subscribe to this mod's changes

release-and-publish is a skill published in the GitHub repository cyanheads/workflows-mcp-server (31 stars, last pushed 6d ago), licensed Apache-2.0. It adds 112 tokens to every session and 3,392 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 124 lines, and is treated as a copy.

Git and workflow Releases Workflow Automation agent-automation ai-agents mcp mcp-server workflow

shipping-and-launch

Prepare production changes with launch checks, staged rollout, rollback, monitoring, and evidence.

Plazmodium/odin-workflow · 21 tokens

flow-next-land

Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.

gmickel/flow-next · 42 tokens

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…

Arenukvern/mcp_flutter · 84 tokens

release-and-publish