Borrowing it
Nothing to install: this file belongs to florian101010/awesome-agentic-AI-coding-template. 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/florian101010/awesome-agentic-AI-coding-template/main/.agent/skills/release-readiness/SKILL.mdgit clone --depth 1 https://github.com/florian101010/awesome-agentic-AI-coding-templateWrote 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/florian101010/awesome-agentic-ai-coding-template/release-readiness)<a href="https://agentmods.dev/skills/florian101010/awesome-agentic-ai-coding-template/release-readiness"><img src="https://agentmods.dev/badge/skills/florian101010/awesome-agentic-ai-coding-template/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/florian101010/awesome-agentic-ai-coding-template/release-readiness"><img src="https://agentmods.dev/badge/skills/florian101010/awesome-agentic-ai-coding-template/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.00030 | $0.00120 |
| Opus 5 | $0.00015 | $0.00060 |
| Sonnet 5 | $0.00006 | $0.00024 |
| Haiku 4.5 | $0.00003 | $0.00012 |
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
Follow .agent/workflows/release-readiness.md strictly.
Execution requirements:
- Confirm release scope/freeze.
- Run full QA checklist and summarize results.
- Validate target environment baseline and compatibility assumptions.
- Run documentation drift check using doc-audit workflow.
- Run pre-commit checks before final recommendation.
- Provide Go/No-Go result with explicit blockers.
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 · 18 lines · 30 tokens per session scan A cfc9127a01af
release-readiness is a skill published in the GitHub repository florian101010/awesome-agentic-AI-coding-template (4 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 120 once invoked, about $0.0002 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
mathodology-dev-test-release
Use when checking skill metadata, references or repository boundaries, or preparing an explicitly requested skills release.
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs.
launch
You are a release engineer. Execute each phase in order. Each must fully complete before advancing. Do NOT ask for permission. Stop only if something is truly unfixable.
gate
MANDATORY before every commit and push. All gates must pass — Gates 1–3 always run; Gates 4 (Docker) and 5 (Cloud) run only when applicable. Do NOT proceed if any gate fails — fix the issue first.
deploy-check
MUST use before any git push to main/master/production, or when user mentions 'deploy', 'going live', 'push to prod', 'ready to ship', 'merge to main', 'release'. Also trigger before any npm publish for CLI tools, or on 'audit', 'check vulnerabilities', 'are our deps safe?', 'npm audit', 'yarn audit'. Performs: test…
changelog
Generate a changelog from git history since a tag, date, or commit.