agentmods.dev

metadome-link: Skill for Claude Code

.claude/skills/release-readiness/SKILL.md

release-readiness is a skill for Claude Code from berntpopp/metadome-link. It costs 21 tokens per session (203 once invoked), scanned A, a copy of release-readiness, MIT.

A release checklist for metadome-link builds. It covers code changes, local checks, container validation, version consistency, documentation, safety, and remaining risks.

In plain words
What is it for?
Use it before tagging, publishing, or promoting a build to run CI and container checks, inspect release files, verify version guards, review MCP safety language, and record residual risks.
Why use it?
It reduces the chance of publishing an unintended, incorrectly versioned, poorly documented, or insufficiently hardened build.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is berntpopp/metadome-link's own configuration. It tells Claude Code how to work on metadome-link itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything metadome-link configures →

not rated 0repo 2d ago A scan 21 tokens copy · 91% MIT
View source ↗ berntpopp/metadome-link genefoundry.org
Reuse

Borrowing it

Nothing to install: this file belongs to berntpopp/metadome-link. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/berntpopp/metadome-link/main/.claude/skills/release-readiness/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/berntpopp/metadome-link

Made for: Claude Code.

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.

agentmods badge for release-readiness

README.md
[![agentmods](https://agentmods.dev/badge/skills/berntpopp/metadome-link/release-readiness/github.svg)](https://agentmods.dev/skills/berntpopp/metadome-link/release-readiness)
Your own site
<a href="https://agentmods.dev/skills/berntpopp/metadome-link/release-readiness"><img src="https://agentmods.dev/badge/skills/berntpopp/metadome-link/release-readiness/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.

agentmods 80×15 button for release-readiness

Your own site · 80×15
<a href="https://agentmods.dev/skills/berntpopp/metadome-link/release-readiness"><img src="https://agentmods.dev/badge/skills/berntpopp/metadome-link/release-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 203 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00203
Opus 5.5 $0.00008 $0.00081
Sonnet 5.5 $0.00004 $0.00041
Haiku 4.5 $0.00002 $0.00020

Measured 1mo ago against content hash a33ae7a2a994, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-readiness 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 1mo 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.

Origin

This is a copy

91% identical to release-readiness — 2 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.

.claude/skills/release-readiness/SKILL.md · 18 lines

What it actually says

Release Readiness

Follow AGENTS.md first.

Workflow

  1. Confirm the worktree holds only intended release changes.
  2. Run make ci-local; build/validate the container (make docker-build plus any docker-*-config validation targets the Makefile exposes).
  3. Verify single-source versioning (../genefoundry-router/docs/VERSIONING-STANDARD-v1.md): the version comes from package metadata and serverInfo.version does not leak the framework version; the version guard test passes.
  4. Check README / CHANGELOG, MCP safety language, and deployment docs for drift.
  5. Confirm any destructive MCP tools remain opt-in and the container overlays stay hardened (../genefoundry-router/docs/CONTAINER-HARDENING-STANDARD-v1.md).
  6. Record residual risks before handoff.
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.

  1. 1mo ago First seen · 18 lines · 21 tokens per session scan A a33ae7a2a994

Subscribe to this mod's changes

release-readiness is a skill published in the GitHub repository berntpopp/metadome-link (0 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 203 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to release-readiness, differing in 2 lines, and is treated as a copy.

Git and workflowReleasesbioinformaticsclaudellm-toolsmcpmodel-context-protocolprotein-domains
Related

Other skills, from other repositories

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…

cyanheads/pubchem-mcp-server · 109 tokens

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…

cyanheads/pubchem-mcp-server · 155 tokens

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/pubchem-mcp-server · 136 tokens

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…

cyanheads/brapi-mcp-server · 109 tokens

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…

cyanheads/brapi-mcp-server · 155 tokens

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…

cyanheads/uniprot-mcp-server · 109 tokens