Borrowing it
Nothing to install: this file belongs to KbWen/agentic-os. 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/KbWen/agentic-os/main/.agents/skills/production-readiness/SKILL.mdgit clone --depth 1 https://github.com/KbWen/agentic-osWrote 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/kbwen/agentic-os/production-readiness)<a href="https://agentmods.dev/skills/kbwen/agentic-os/production-readiness"><img src="https://agentmods.dev/badge/skills/kbwen/agentic-os/production-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/kbwen/agentic-os/production-readiness"><img src="https://agentmods.dev/badge/skills/kbwen/agentic-os/production-readiness.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.00023 | $0.00834 |
| Opus 5 | $0.00012 | $0.00417 |
| Sonnet 5 | $0.00005 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
production-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- production-readiness — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Readiness
Overview
Code that passes all tests but logs errors only via debug-only APIs (e.g., debugPrint, console.log in debug mode) is functionally silent in production. This skill enforces observability readiness before ship — ensuring the team is not blind during beta testing and production rollout.
When to Use
- Auto-recommended for
featureandarchitecture-changeclassifications. - Activate manually when working on error handling, crash reporting, or logging infrastructure.
- Apply at
/review(semantic error check) and/ship(readiness checklist).
Observability Checklist
1. Error Surface Audit (at /review)
For every catch / error-handling block in changed files:
| Check | Pass | Fail |
|---|---|---|
| Logging call exists | Logger.error(), log.error(), crashReporter.capture() |
Empty catch {} |
| Logger is production-observable | Framework logger, crash reporter, structured stdout | debugPrint(), print(), debug-only console.log |
| Error context is actionable | Includes error type, operation, identifiers | "error occurred", raw exception only |
2. Log Sink Documentation (at /ship)
Document in Work Log where production errors go:
## Observability
- Error sink: [e.g., Sentry via Logger.error(), Crashlytics, stdout → CloudWatch]
- Health check: [e.g., /health endpoint, Firebase Vitals, uptime monitor]
- Rollback signal: [e.g., error rate > 2x baseline → revert]
If the project has no production logging infrastructure, document as Known Risk:
"No production error reporting configured. Errors in catch blocks will be logged to stdout only. Risk: silent failures in release builds if stdout is not monitored."
3. Rollback Telemetry (at /ship)
The rollback plan (per engineering_guardrails.md §12.5) must answer:
- How will operators know the rollback is needed? (alert, dashboard, manual check)
- How will operators know the rollback succeeded? (error rate drops, health check passes)
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 · 79 lines · 23 tokens per session scan A dd1f151bd3b2
production-readiness is a skill published in the GitHub repository KbWen/agentic-os (160 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 834 once invoked, about $0.0001 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
muster-frappe-metadata
Design, generate, review, apply, and roll back Frappe or ERPNext metadata changes through Muster. Use for DocTypes, child tables, custom fields, property setters, workflows, roles, permissions, reports, print formats, web pages, workspaces, fixtures, patches, or installed-app compatibility.
muster-frappe-orchestrator
Coordinate end-to-end Muster automation work across Frappe or ERPNext architecture, metadata, UI, workflows, security, testing, deployment, and evidence. Use for cross-cutting features, production plans, multi-agent delivery, or work that spans Muster core and a Frappe app.
muster-frappe-release
Build, seed, deploy, break, measure, and prove a Muster Frappe release. Use for bench or site setup, migrations, realistic ERPNext data, role matrices, browser/mobile QA, performance and recovery tests, release evidence, Frappeverse demos, or normal-speed presentation video.
muster-frappe-security
Threat-model and negatively verify Muster integrations with Frappe OAuth, multi-tenancy, RBAC, field permissions, agent delegation, channels, secrets, approvals, and audit logs. Use for identity linking, site registration, Telegram onboarding, policy changes, permission tests, or security release gates.
muster-frappe-workflows
Design and implement durable multi-step Muster workflows for Frappe with agent, subagent, and nested task graphs. Use for workflow definitions, planning, delegation, tool policies, approvals, retries, schedules, triggers, artifacts, dynamic page creation, or Claude-style universal JS and JSON automation.
muster-frappe-ui
Build and validate Muster's native Frappe v16 desktop, Desk, and mobile automation experience. Use for the activity sidecar, mission control, agent/workflow screens, realtime progress, previews, approvals, dynamic pages, accessibility, or responsive interaction design.