What is release-and-publish?

A release workflow that verifies and publishes a prepared software version to its configured package and code registries.

Use it after version changes, changelog updates, a release commit, and an annotated Git tag are already complete, to push and publish the release to applicable npm, MCP Registry, GitHub Releases, and container registry destinations.

Publishing involves several checks and destinations, so this workflow catches missing release preparation before sending the version out.

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/ensembl-mcp-server --skill release-and-publish

Clone the repo

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

Made for: Claude Code.

Or install ensembl-mcp-server, the plugin that ships this one along with the rest of its 33 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/ensembl-mcp-server/release-and-publish/github.svg)](https://agentmods.dev/skills/cyanheads/ensembl-mcp-server/release-and-publish)

Your own site

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

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

When invoked 6,309 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.00155	$0.06309
Opus 5.5	$0.00062	$0.02524
Sonnet 5.5	$0.00031	$0.01262
Haiku 4.5	$0.00015	$0.00631

Measured 7d ago against content hash d3dad7825fee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf -m 15 -o /dev/null "https://registry.npmjs.org/<package-name>/<version>" && echo served && break

Origin

This is a copy

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

framework-skills/release-and-publish/SKILL.md · 330 lines

How it starts

The opening of the file, as written. The whole thing — 330 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): <version> — <theme>) is at HEAD — or, in gated release PR mode, reachable from HEAD with only the review pass's commits above it
No tag exists yet — this skill creates it (step 4)
Working tree is clean
Release PR mode (see git-wrapup's "Release PR mode"): HEAD is on release/<version>, the branch is pushed, the PR is open, and — in gated mode — the caller has confirmed the review pass is finished. Without that confirmation, halt: this skill never decides on its own that a review is done.

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 5–9 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 9), run docker builder prune -f to drop any cached corrupt layer. Skip this extra step for other retries.

Never retry on idempotent-success signals

Read the full file on GitHub · 330 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.

7d ago Changed d3dad7825fee
17d ago Changed · +4 lines 94d7430b6fe0
1mo ago Changed · +102 lines · +43 tokens per session 03fb2a0af188
1mo ago First seen · 224 lines · 112 tokens per session scan A d59a54e65293

Subscribe to this mod's changes

release-and-publish is a skill published in the GitHub repository cyanheads/ensembl-mcp-server (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 155 tokens to every session and 6,309 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 92% identical to release-and-publish, differing in 4 lines, and is treated as a copy.

DevOps and cloud Ensembl Git and workflow Releases ai-agents ai-tools bioinformatics cyanheads genes

release-pr-review

Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…

cyanheads/gdelt-mcp-server · 136 tokens