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.
npx skills add 05-deepak-patidar/claude-skills --skill release-readinessgit clone --depth 1 https://github.com/05-deepak-patidar/claude-skillsWrote 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/05-deepak-patidar/claude-skills/release-readiness)<a href="https://agentmods.dev/skills/05-deepak-patidar/claude-skills/release-readiness"><img src="https://agentmods.dev/badge/skills/05-deepak-patidar/claude-skills/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/05-deepak-patidar/claude-skills/release-readiness"><img src="https://agentmods.dev/badge/skills/05-deepak-patidar/claude-skills/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.00079 | $0.01050 |
| Opus 5 | $0.00039 | $0.00525 |
| Sonnet 5 | $0.00016 | $0.00210 |
| Haiku 4.5 | $0.00008 | $0.00105 |
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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness
"Done" and "ready for real users" are different claims. This skill is the go/no-go gate: a structured sweep that turns "I think it's ready" into a checked list with evidence. Run it before first launch, before major releases, and before handing anything to a paying client.
How to run it
Work through the seven gates below against evidence, not memory — for each item, the answer is a command output, a file path, a screenshot, or a tested behavior, never "yes, I'm pretty sure". Produce a written verdict at the end: ✅ ready / ⚠️ ready-with-known-risks (listed, accepted by the user) / ❌ blocked (by what). Deep-dive any failing gate with its dedicated skill (threat-model-security, deployment-safety, observability-readiness, etc.).
Gate 1 — Correctness of the money-and-data core
- Golden paths run end-to-end in a production-like environment, by hand, today — not "tests passed last week".
- Money math spot-checked against a calculator: one real invoice with discounts/tax/rounding, one payment, one return.
- Concurrent/duplicate actions tried: double-click submit, retry after timeout, two tabs. No dupes, no corruption.
- Test suite green from clean checkout; the regression tests for every previously found bug still exist and pass.
Gate 2 — Security minimum (threat-model-security)
- The IDOR test performed live: user A's token requesting user B's objects on every resource type → refused.
- Auth rate-limiting/lockout demonstrated, not assumed. Sessions revocable.
- Secrets audit: none in git history/client bundle/logs; prod secrets differ from dev; HTTPS enforced.
- Error responses leak nothing internal (trigger a 500 deliberately and look).
Gate 3 — Data safety (database-design)
- Backups: running, automatic, AND restored once successfully into a scratch environment — an untested backup is a hope, not a backup.
- Destructive operations inventoried: what can permanently delete/overwrite data, and what protects each (confirm, soft-delete, audit row)?
- The DB enforces its own invariants: spot-check that constraints exist in the live schema (not just in models).
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.
- 12d ago First seen · 57 lines · 79 tokens per session scan A 5e766291a4c0
release-readiness is a skill published in the GitHub repository 05-deepak-patidar/claude-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 1,050 once invoked, about $0.0004 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
plan-pipeline-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.
plan-pipeline-eng-review
Engineering architecture gate: lock architecture, diagrams, edge cases, and test matrix before writing implementation code.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
generate-tests
Generate comprehensive tests for specified code.
ci-tests
Run the test suite for the current repo, auto-detecting Python (pytest/uv), Node (vitest/pnpm), or Rust (cargo test).