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 Nordic-AI/production-readiness-skills --skill release-readinessgit clone --depth 1 https://github.com/Nordic-AI/production-readiness-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/nordic-ai/production-readiness-skills/release-readiness)<a href="https://agentmods.dev/skills/nordic-ai/production-readiness-skills/release-readiness"><img src="https://agentmods.dev/badge/skills/nordic-ai/production-readiness-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/nordic-ai/production-readiness-skills/release-readiness"><img src="https://agentmods.dev/badge/skills/nordic-ai/production-readiness-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.00151 | $0.05379 |
| Opus 5 | $0.00076 | $0.02690 |
| Sonnet 5 | $0.00030 | $0.01076 |
| Haiku 4.5 | $0.00015 | $0.00538 |
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 — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness Audit
You review whether changes can reach production safely and be reversed safely when they shouldn't. Most production incidents happen at or shortly after release — release readiness is about making that event boring.
This skill follows the library-wide rules in docs/CONVENTIONS.md. Read that first.
Inputs
From orchestrator: scope_tier, stack_summary, gitnexus_indexed, deployment target.
If user invokes directly, gather: CI/CD platform, deployment target (k8s, ECS, serverless, bare VMs, etc.), release cadence, rollback expectations (how fast do incidents need to be reversible).
Finding ID prefix
REL-R — see CONVENTIONS.md §4.
Tier thresholds
| Tier | Automated CI | Automated deploy | Rollback mechanism | Feature flags | Canary/gradual | Migration safety |
|---|---|---|---|---|---|---|
| prototype | tests run | manual OK | documented procedure OK | optional | optional | review required |
| team | tests + lint + security scans gating | automated from main | single command / button | required for risky changes | recommended | online-compatible required |
| scalable | required + artifact signing | required + progressive | automatic on SLO burn | required + per-segment | required | required + tested on prod-scale replica |
Review surface
1. CI pipeline quality
A PR landing on main without green CI is an immediate red flag.
- Required status checks on main:
- Unit tests
- Lint
- Type check (where applicable)
- Build
- Security scans (cross-reference
supply-chain-audit,security-audit) - Skill-specific: e2e tests for user-facing apps, eval regression for AI apps
- Branch protection enforces the checks (the checks existing without enforcement is the most common false-sense-of-security pattern).
- Flaky-test tolerance: flake rate measured; retries permitted but not infinite. Flaky tests quarantined with an owner and deadline, not ignored.
- Speed: CI feedback time measured. Target <10 min to first failure signal at team+ tier; <20 min to full green. Slow CI means skipped CI.
- Parallelization used — test sharding, matrix builds.
- Caching — dependency cache, build cache, layer cache. Speeds CI without sacrificing correctness.
- No "emergency skip" merge button without at least a paper trail and post-merge verification.
- Secrets in CI scoped to jobs that need them; not exposed in logs (see
supply-chain-audit).
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 · 440 lines · 151 tokens per session scan A 8869b5dbfd9d
release-readiness is a skill published in the GitHub repository Nordic-AI/production-readiness-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 151 tokens to every session and 5,379 once invoked, about $0.0008 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
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
gdpr-compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing Agreements (DPAs), and consent notices, (3) answering GDPR compliance questions with authoritative article citations, and…
iso42001
Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
nist-800-53
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200 system categorization, control tailoring and overlays, privacy controls (PT family), supply chain risk management (SR…
soc2
Expert SOC 2 compliance assistant covering all five Trust Services Criteria (Security/CC, Availability/A, Confidentiality/C, Processing Integrity/PI, Privacy/P). Use this skill whenever a user mentions SOC 2, Trust Services Criteria, SOC 2 Type 1 or Type 2, audit readiness, compliance gaps, control documentation…