Borrowing it
Nothing to install: this file belongs to YankielDBC2/codex-skills-library. 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/YankielDBC2/codex-skills-library/main/.agents/skills/release-readiness-check/SKILL.mdgit clone --depth 1 https://github.com/YankielDBC2/codex-skills-libraryWrote 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/yankieldbc2/codex-skills-library/release-readiness-check)<a href="https://agentmods.dev/skills/yankieldbc2/codex-skills-library/release-readiness-check"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/release-readiness-check.svg" alt="Measured on agentmods" 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.00027 | $0.00282 |
| Opus 5 | $0.00014 | $0.00141 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
release-readiness-check 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 8d 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 Check
Goal
Catch release blockers before a project is shipped.
When to use
Use before deploying a website, merging a major feature, publishing a package, or handing a project to a client.
When not to use
Do not use for early prototypes where speed matters more than launch quality.
Inputs
Inspect release notes, changed files, package scripts, env requirements, tests, docs, deployment config, and user-facing flows.
Workflow
- Identify what is being released.
- Check build, tests, lint, and typecheck.
- Check environment variables and deployment configuration.
- Check user-facing flows and error states.
- Check security and secret exposure.
- Check docs and handoff instructions.
- Separate blockers from nice-to-have improvements.
- Produce a concise go/no-go summary.
Quality bar
A good readiness check is practical, prioritized, and honest about uncertainty.
Validation
Run the release's required validation commands and any targeted smoke checks.
Final response
Report go/no-go status, blockers, non-blocking improvements, validation output, and deployment notes.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 49 lines · 27 tokens per session scan A 167c374633da
release-readiness-check is a skill published in the GitHub repository YankielDBC2/codex-skills-library (10 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 282 once invoked, about $0.0001 per session on Opus 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
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.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
create-release
Use when the user asks to "create a release", "cut a release", "tag a version", "publish release notes", or ship a new versioned GitHub release for the current repo.
sync-docs-release
Use when the user wants to sync docs and then cut a release in one shot. Combines sync-docs → land the doc changes (branch + PR, or a direct commit when the repo allows it) → create-release in sequence. Triggers on phrases like "sync docs and release", "sync and cut a release", "update docs and publish a release".