Borrowing it
Nothing to install: this file belongs to berntpopp/genefoundry-router. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/berntpopp/genefoundry-router/main/.claude/skills/release-readiness/SKILL.mdgit clone --depth 1 https://github.com/berntpopp/genefoundry-routerWrote 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/berntpopp/genefoundry-router/release-readiness)<a href="https://agentmods.dev/skills/berntpopp/genefoundry-router/release-readiness"><img src="https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/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.
<a href="https://agentmods.dev/skills/berntpopp/genefoundry-router/release-readiness"><img src="https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/release-readiness.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.00022 | $0.00219 |
| Opus 5.5 | $0.00009 | $0.00088 |
| Sonnet 5.5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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.
What it actually says
Release Readiness (router)
Follow AGENTS.md first.
Workflow
- Confirm the worktree holds only intended release changes.
make ci-local; thenmake docker-buildand anydocker-*-configvalidation targets the Makefile exposes.make fleet-probe— confirm every enabled backend is reachable and harvests a non-zero tool set (closes the CI≠prod gap);make list-toolsfor the namespaced surface.make snapshot-catalogand review; re-pin the drift baseline (make snapshot-baseline) only after reviewing the diff.- Verify single-source versioning (no
serverInfo.versionframework leak) and hardened container overlays (ports: !reset [], cap-drop, read-only). - Confirm the auth posture for the target env (edge auth on for public; secure-by-default guard intact); record residual risks.
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.
- 1mo ago First seen · 18 lines · 22 tokens per session scan A 4f57a0421b95
release-readiness is a skill published in the GitHub repository berntpopp/genefoundry-router (6 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 219 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
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…
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…
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…
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…
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…