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 OneDro1d/dark-factory --skill production-readiness-reviewergit clone --depth 1 https://github.com/OneDro1d/dark-factoryWrote 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/onedro1d/dark-factory/production-readiness-reviewer)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/production-readiness-reviewer"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/production-readiness-reviewer/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/onedro1d/dark-factory/production-readiness-reviewer"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/production-readiness-reviewer.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.00075 | $0.01443 |
| Opus 5 | $0.00037 | $0.00722 |
| Sonnet 5 | $0.00015 | $0.00289 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
production-readiness-reviewer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8080/health | jq How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Readiness Reviewer
Verify whether a service, feature, or smart contract is safe to deploy to production. Ensures all operational, reliability, and safety requirements are met before go-live.
Core Guardrails
:red_circle: If rollback is impossible, it's a red flag. :red_circle: If you can't observe it, you can't operate it.
When to Use
- Preparing a service for first production deployment
- Reviewing release candidates before deploy
- Validating production configuration changes
- Pre-launch checklist for new features
- Smart contract deployment verification
- Infrastructure changes going to production
Review Workflow
On EVERY invocation, execute these steps in order:
Step 1: Identify Deployable Unit
Determine what is being deployed:
| Type | Examples |
|---|---|
| Service | API, worker, microservice, lambda |
| Frontend | Web app, mobile app build |
| Smart Contract | Solidity, Vyper, Rust/Anchor |
| Infrastructure | Terraform, K8s manifests, cloud resources |
| Configuration | Feature flags, env vars, secrets |
| Database | Migration, schema change |
Document:
Deployable: [name]
Type: [service/frontend/contract/infra/config/database]
Version: [tag/commit/hash]
Target environment: [staging/production]
Step 2: Inspect Configuration
Review all configuration for production readiness:
# Find environment variables
grep -rn "process.env\|os.environ\|env::" --include="*.ts" --include="*.py" --include="*.go"
# Find config files
ls -la *.config.* .env* config/ 2>/dev/null
# Check for hardcoded values
grep -rn "localhost\|127.0.0.1\|:3000\|:8080" --include="*.ts" --include="*.yaml"
# Find feature flags
grep -rn "feature.*flag\|isEnabled\|FF_" --include="*.ts" --include="*.tsx"
Verify:
- All env vars documented and have production values
- No hardcoded development URLs/ports
- Secrets come from vault/env, not code
- Feature flags set correctly for production
- Resource limits configured (memory, CPU, connections)
What ships with it
2 files 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 · 196 lines · 75 tokens per session scan A 001b0f22577c
production-readiness-reviewer is a skill published in the GitHub repository OneDro1d/dark-factory (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 1,443 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.