Borrowing it
Nothing to install: this file belongs to KbWen/agent-virtual-office. 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/agent-virtual-office/main/.agents/skills/production-readiness/SKILL.mdgit clone --depth 1 https://github.com/KbWen/agent-virtual-officeWrote 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/agent-virtual-office/production-readiness)<a href="https://agentmods.dev/skills/kbwen/agent-virtual-office/production-readiness"><img src="https://agentmods.dev/badge/skills/kbwen/agent-virtual-office/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/agent-virtual-office/production-readiness"><img src="https://agentmods.dev/badge/skills/kbwen/agent-virtual-office/production-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.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 11d 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.
This is a copy
100% identical to production-readiness — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 11d ago First seen · 79 lines · 23 tokens per session scan A dd1f151bd3b2
production-readiness is a skill published in the GitHub repository KbWen/agent-virtual-office (18 stars, last pushed 2d ago), 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. It is 100% identical to production-readiness, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
devtools-bidirectional
Two-way event patterns between devtools panel and application. App-to-devtools observation, devtools-to-app commands, time-travel debugging with snapshots and revert. structuredClone for snapshot safety, distinct event suffixes for observation vs commands, serializable payloads only.
devtools-instrumentation
Analyze library codebase for critical architecture and debugging points, add strategic event emissions. Identify middleware boundaries, state transitions, lifecycle hooks. Consolidate events (1 not 15), debounce high-frequency updates, DRY shared payload fields, guard emit() for production. Transparent server/client…
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
copilotkit-debug
Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
therapeutic-ifs
Unified inner work engine: Schema deconstruction (diagnosis) + IFS therapy (treatment). Absorbs: schema-deconstruction.