agentmods.dev

clingen-link: Skill for Claude Code

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

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

A release checklist for preparing a clingen-link build for tagging, publishing, or promotion. A release is a version of the software prepared for users or deployment.

In plain words
What is it for?
Use it to run release checks, validate Docker builds and configuration, verify version reporting, review documentation, and confirm container and data-change safeguards.
Why use it?
It helps confirm that only intended changes are included, the build and container are valid, documentation matches the code, and known risks are recorded.

Skill for Claude Code

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

This is berntpopp/clingen-link's own configuration. It tells Claude Code how to work on clingen-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 clingen-link configures →

not rated 0repo 5d ago A scan 20 tokens copy · 92% MIT
View source ↗ berntpopp/clingen-link genefoundry.org
Reuse

Borrowing it

Nothing to install: this file belongs to berntpopp/clingen-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/clingen-link/main/.claude/skills/release-readiness/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/berntpopp/clingen-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/clingen-link/release-readiness/github.svg)](https://agentmods.dev/skills/berntpopp/clingen-link/release-readiness)
Your own site
<a href="https://agentmods.dev/skills/berntpopp/clingen-link/release-readiness"><img src="https://agentmods.dev/badge/skills/berntpopp/clingen-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/clingen-link/release-readiness"><img src="https://agentmods.dev/badge/skills/berntpopp/clingen-link/release-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 202 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 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00202
Opus 5 $0.00010 $0.00101
Sonnet 5 $0.00004 $0.00040
Haiku 4.5 $0.00002 $0.00020

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

92% 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. 9d ago First seen · 18 lines · 20 tokens per session scan A 534a875c448a

Subscribe to this mod's changes

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

Git and workflowReleasesbioinformaticsclingengene-curationgenomicsmcpmodel-context-protocol
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) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…

cyanheads/gnomad-genetics-mcp-server · 82 tokens

maintenance

Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…

cyanheads/gnomad-genetics-mcp-server · 75 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) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…

cyanheads/uniprot-mcp-server · 82 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, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…

cyanheads/gnomad-genetics-mcp-server · 112 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, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…

cyanheads/uniprot-mcp-server · 112 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). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…

cyanheads/obsidian-mcp-server · 104 tokens