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 jnPiyush/AgentX --skill production-readinessgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/production-readiness)<a href="https://agentmods.dev/skills/jnpiyush/agentx/production-readiness"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/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/jnpiyush/agentx/production-readiness"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/production-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 147 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 141 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00042 | $0.03826 |
| Opus 5.5 | $0.00017 | $0.01530 |
| Sonnet 5.5 | $0.00008 | $0.00765 |
| Haiku 4.5 | $0.00004 | $0.00383 |
Grade A, and why
production-readiness 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 1mo 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.
| Health endpoint | `curl /api/health` | 200 OK with service details | How it starts
The opening of the file, as written. The whole thing — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Readiness
Purpose: Certify that a release meets all quality, security, performance, and operational criteria for production deployment. Scope: Quality gates, release checklists, chaos testing, rollback validation, observability, go/no-go decisions.
When to Use This Skill
- Certifying a release candidate for production
- Running pre-release quality gates
- Validating rollback and recovery procedures
- Performing chaos/resilience testing
- Verifying observability and alerting
- Making go/no-go deployment decisions
- Post-deployment validation
When NOT to Use
- Writing feature tests (use e2e/integration testing)
- Building CI pipelines (use test automation)
- Initial security scanning (use security testing)
- Performance benchmarking (use performance testing)
Prerequisites
- All feature development complete (code freeze)
- Test suites passing (unit, integration, e2e)
- Security scans completed (SAST, DAST, SCA)
- Performance baselines established
- Staging environment matching production topology
Decision Tree
Production readiness task?
+-- Pre-release certification?
| +-- All tests passing? -> Run quality gate pipeline
| +-- Security scans done? -> Check SAST, SCA, secret scan results
| +-- Performance validated? -> Run smoke load test against staging
+-- Rollback validation?
| +-- Database migrations? -> Test expand-contract rollback
| +-- Stateless deploy? -> Verify previous image redeploy
| +-- Feature flags? -> Test flag disable path
+-- Chaos / resilience testing?
| +-- Upstream dependency failure? -> Inject latency and 5xx errors
| +-- Infrastructure failure? -> Simulate pod kill, network partition
| +-- Data store failure? -> Test connection drop and recovery
+-- Go/no-go decision?
+-- Score all categories -> Use weighted decision matrix
+-- Any category below 3? -> NO-GO, remediate first
+-- Total >= 4.0? -> GO with documented risks
Production Readiness Checklist
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.
- 1mo ago First seen · 470 lines · 42 tokens per session scan A cfb78b3bb808
production-readiness is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 3,826 once invoked, about $0.0002 per session on Opus 5.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-03.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.