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.
git 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/commands/nwiizo/ccswarm/check-production-ready)<a href="https://agentmods.dev/commands/nwiizo/ccswarm/check-production-ready"><img src="https://agentmods.dev/badge/commands/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/commands/nwiizo/ccswarm/check-production-ready"><img src="https://agentmods.dev/badge/commands/nwiizo/ccswarm/check-production-ready.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.00000 | $0.00869 |
| Opus 5 | $0.00000 | $0.00434 |
| Sonnet 5 | $0.00000 | $0.00174 |
| Haiku 4.5 | $0.00000 | $0.00087 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Readiness Check
Verifies ccswarm's production quality criteria.
Check Items
7 quality criteria based on CLAUDE.md:
| # | Item | Criteria | Check Command |
|---|---|---|---|
| 1 | unwrap() elimination | Forbidden in production code | grep -r "\.unwrap()" crates/ccswarm/src/ |
| 2 | Result/Error handling | Custom error types with thiserror | grep -r "thiserror" crates/ |
| 3 | Async patterns | tokio runtime, async-trait | cargo check |
| 4 | Documentation | rustdoc for public APIs | cargo doc --workspace |
| 5 | Clippy clean | No warnings | cargo clippy --workspace -- -D warnings |
| 6 | Channel-Based | Prefer Channel over Arc | grep -r "Arc<Mutex" crates/ |
| 7 | Minimal tests | Around 8-10 tests | `cargo test --workspace 2>&1 |
Execution Method
# 1. unwrap() check
echo "=== unwrap() count ==="
grep -r "\.unwrap()" crates/ccswarm/src/ --include="*.rs" | grep -v "test" | wc -l
# 2. Error handling verification
echo "=== thiserror usage ==="
grep -r "use thiserror" crates/
# 3. Clippy check
echo "=== Clippy check ==="
cargo clippy --workspace -- -D warnings
# 4. Documentation generation
echo "=== Documentation ==="
cargo doc --workspace --no-deps
# 5. Arc<Mutex> count
echo "=== Arc<Mutex> count ==="
grep -r "Arc<Mutex" crates/ccswarm/src/ | wc -l
# 6. Test count verification
echo "=== Test count ==="
cargo test --workspace 2>&1 | grep "test result"
Output Format
{
"production_ready": {
"unwrap_elimination": {
"status": "OK|NG",
"count": N,
"locations": ["problem locations"]
},
"error_handling": {
"status": "OK|NG",
"thiserror_used": true|false,
"custom_errors": ["ErrorType1", "ErrorType2"]
},
"async_patterns": {
"status": "OK|NG",
"tokio_version": "1.x",
"async_trait_used": true|false
},
"documentation": {
"status": "OK|NG",
"public_api_coverage": "N%"
},
"clippy_clean": {
"status": "OK|NG",
"warnings": N,
"errors": N
},
"channel_based": {
"status": "OK|NG",
"arc_mutex_count": N,
"channel_usage": N,
"ratio": "channels/arc_mutex"
},
"minimal_testing": {
"status": "OK|NG",
"test_count": N,
"target_range": "8-10"
}
},
"score": "N/7",
"overall_status": "PRODUCTION_READY|NEEDS_WORK|CRITICAL"
}
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 · 115 lines · 0 tokens per session scan A 819d7a5c1a8d
check-production-ready is a command published in the GitHub repository nwiizo/ccswarm (151 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 869 tokens. 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 commands, from other repositories
cargo-bench
Command "cargo-bench" from olorehq/olore, covering cargo-bench(1), name, synopsis, description and working directory of benchmarks.
cargo-test
Command "cargo-test" from olorehq/olore, covering cargo-test(1), name, synopsis, description and documentation tests.
test-rust
Run Rust tests for Solana programs and backend services.
cargo-miri
Command "cargo-miri" from olorehq/olore, covering cargo-miri(1), name, description and see also.
rust-test
Enforce TDD workflow for Rust. Write tests first, then implement. Verify 80%+ coverage with cargo-llvm-cov.
rust-test
Enforce TDD workflow for Rust. Write tests first, then implement. Verify 80%+ coverage with cargo-llvm-cov.