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 caipe-io/ai-platform-engineering --skill release-readiness-checkgit clone --depth 1 https://github.com/caipe-io/ai-platform-engineeringWrote 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/caipe-io/ai-platform-engineering/release-readiness-check)<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/release-readiness-check"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/release-readiness-check/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/caipe-io/ai-platform-engineering/release-readiness-check"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/release-readiness-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.00539 |
| Opus 5 | $0.00027 | $0.00269 |
| Sonnet 5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
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 10d 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
Orchestrate GitHub, ArgoCD, and Jira agents to perform a comprehensive pre-release verification covering code readiness, environment health, and issue resolution.
Instructions
Phase 1: Code Readiness (GitHub Agent)
- Check open PRs targeting release branch
- CI/CD status on the release branch
- Recent commits and conventional commit compliance
- Release artifacts - changelog, version bump, Docker images
Phase 2: Environment Health (ArgoCD Agent)
- Staging environment - synced, healthy, correct version
- Production environment baseline - healthy before deploying
- Helm chart versions updated
Phase 3: Issue Resolution (Jira Agent)
- Blocking issues - release-blockers, p0
- Testing status - QA sign-off, regression results
- Documentation - release notes, breaking changes, ADRs
Phase 4: Release Verdict
Compile all checks into a Go/No-Go decision with clear justification.
Output Format
```markdown
Release Readiness Report
Release: v2.4.0 Verdict: GO / NO-GO / CONDITIONAL
Readiness Checklist
| Category | Check | Status | Details |
|---|---|---|---|
| Code | All PRs merged | PASS | 0 open PRs |
| Code | CI checks passing | PASS | All 12 checks green |
| Env | Staging healthy | PASS | All 15 apps synced |
| Issues | No release blockers | FAIL | 1 blocker open |
| ``` |
Examples
- "Are we ready for a release?"
- "Check release readiness for v2.4.0"
- "Is staging healthy and can we deploy to production?"
- "Are there any release blockers in Jira?"
Guidelines
- A single failing critical check makes the verdict NO-GO
- Warnings make the verdict CONDITIONAL (can proceed with acknowledgment)
- Always include a rollback plan in the readiness report
- Check for breaking changes and verify they have corresponding ADRs
- Never skip the staging health check
- Include DCO sign-off verification for all commits in the release
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.
- 10d ago First seen · 61 lines · 54 tokens per session scan A 442d992b33f2
release-readiness-check is a skill published in the GitHub repository caipe-io/ai-platform-engineering (408 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 539 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-30.
Other skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
pipe
Designing GitHub Actions workflows in depth: trigger strategy, security hardening, performance optimization, PR automation, and Reusable Workflow design.
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.