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 nwiizo/ccswarm --skill check-production-readygit clone --depth 1 https://github.com/nwiizo/ccswarmWrote 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/nwiizo/ccswarm/check-production-ready)<a href="https://agentmods.dev/skills/nwiizo/ccswarm/check-production-ready"><img src="https://agentmods.dev/badge/skills/nwiizo/ccswarm/check-production-ready/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/nwiizo/ccswarm/check-production-ready"><img src="https://agentmods.dev/badge/skills/nwiizo/ccswarm/check-production-ready.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.00027 | $0.00270 |
| Opus 5 | $0.00014 | $0.00135 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
check-production-ready 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.
What it actually says
When subagents are enabled in Codex, prefer delegating this workflow to the rust-fix-agent custom agent.
Verify 7 production quality criteria:
| # | Item | Check |
|---|---|---|
| 1 | unwrap() elimination | grep -r "\.unwrap()" crates/ccswarm/src/ --include="*.rs" (exclude tests) |
| 2 | Error handling | thiserror usage, custom error types |
| 3 | Async patterns | tokio runtime, proper async usage |
| 4 | Documentation | cargo doc --workspace --no-deps |
| 5 | Clippy clean | cargo clippy --workspace -- -D warnings |
| 6 | Channel-Based | Channel vs Arc ratio |
| 7 | Minimal testing | ~8-10 focused tests |
Score: 7/7 = PRODUCTION_READY, 5-6/7 = NEEDS_WORK, 0-4/7 = CRITICAL.
Fix any issues found, then report results as JSON.
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 · 26 lines · 27 tokens per session scan A b946142aa426
check-production-ready is a skill published in the GitHub repository nwiizo/ccswarm (151 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 270 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
rust-check
Run cargo check on the current Rust project to find compile errors.
stack-trace-rust-probe
Internal helper for meta-stack-trace-investigator. Use when a Rust panic or backtrace needs Rust-specific Result/Option checks, cargo test guidance, and patch targets.
hotpath_init
Configure hotpath profiling in a Rust project. Adds the hotpath dependency with feature-gated setup, instruments main with hotpath::main, functions with measure/measureall, and wraps channels, mutexes, rwlocks, streams, futures, reqwest clients, axum routers and byte-level I/O with hotpath macros. Use when the user…
memory-safety-patterns
Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.
windows-compat
Audit and harden this Rust repo (code-graph-mcp) for Windows correctness: path-spelling drift between producers, the 32,767-char command-line cap, index-key mismatches, and path predicates that assume one ecosystem's layout. Use whenever touching code that builds, compares, prints, or stores a filesystem path; that…
re-zig
A guide to examining compiled Zig programs, including how Zig-specific error handling, panics, compile-time code, and C interfaces appear in machine code. Reverse engineering means studying a compiled program to understand its behaviour.