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 Eilodon/DPS-Superskills-MCP --skill release-readinessgit clone --depth 1 https://github.com/Eilodon/DPS-Superskills-MCPWrote 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/eilodon/dps-superskills-mcp/release-readiness)<a href="https://agentmods.dev/skills/eilodon/dps-superskills-mcp/release-readiness"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/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/eilodon/dps-superskills-mcp/release-readiness"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/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.00058 | $0.00456 |
| Opus 5 | $0.00029 | $0.00228 |
| Sonnet 5 | $0.00012 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
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.
What it actually says
Release-Readiness — Operational Gate Before Production
Register: DISCIPLINE Goal: Distinguish code complete from release ready. Core principle: production failures often happen during rollout, not implementation.
Announce: "Using release-readiness to verify operational safety before release."
Required for
- C3/C4 tasks before merge or deploy;
- migrations or data backfills;
- feature flag enablement;
- external integration rollout;
- payment, auth, PII, secrets, payment/regulated data, compliance, or irreversible changes.
Checklist
[ ] Rollback path exists and is realistic.
[ ] Feature flag / kill switch considered.
[ ] Migration reversible, backed up, or explicitly accepted as irreversible.
[ ] Smoke test commands defined.
[ ] Observability exists for the changed behavior.
[ ] Alerts or watch signals link to ADR volatility/assumptions.
[ ] Post-deploy verification planned.
[ ] Owner/on-call/runbook identified.
[ ] External dependencies checked.
[ ] User/data impact assessed.
[ ] `privacy-secrets-gate` completed when data sensitivity is 2/3, secrets/PII/payment/regulated data may appear, or external disclosure is planned.
[ ] Known residual risk is labeled with claim grammar.
If any C4 item is missing, do not release until explicit acceptance is recorded.
Output
RELEASE READINESS
Status: READY | READY_WITH_ACCEPTED_RISK | NOT_READY
Evidence:
Rollback:
Smoke tests:
Observability:
Post-deploy verification:
Residual risk:
Completion language must distinguish:
code complete;verified locally;release ready;deployed and verified.
Gotchas — Observed Failure Points
What ships with it
1 file 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.
- 9d ago First seen · 70 lines · 58 tokens per session scan A e3a012cc03ad
release-readiness is a skill published in the GitHub repository Eilodon/DPS-Superskills-MCP (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 456 once invoked, about $0.0003 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.