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-impl)<a href="https://agentmods.dev/commands/nwiizo/ccswarm/check-impl"><img src="https://agentmods.dev/badge/commands/nwiizo/ccswarm/check-impl/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-impl"><img src="https://agentmods.dev/badge/commands/nwiizo/ccswarm/check-impl.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.00327 |
| Opus 5.5 | $0.00000 | $0.00131 |
| Sonnet 5.5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
check-impl 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 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.
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
Implementation Check
Runs basic checks on the ccswarm workspace.
Execution Content
# 1. Format/Lint
cargo fmt --all --check && cargo clippy --workspace -- -D warnings
# 2. Tests
cargo test --workspace
# 3. Build verification
cargo build --workspace --release
Check Items
| Item | Command | Criteria |
|---|---|---|
| Format | cargo fmt --all --check |
No errors |
| Lint | cargo clippy --workspace -- -D warnings |
No warnings |
| Tests | cargo test --workspace |
All pass |
| Build | cargo build --workspace |
No errors |
Rust 2024 Edition Support
ccswarm uses Rust 2024 Edition. Note the following:
std::env::set_varrequiresunsafeblock- Pattern matching has implicit borrowing so
ref/ref mutare unnecessary - Explicit type annotations are required more often
Output Format
{
"format": "OK|NG",
"clippy": {
"warnings": N,
"errors": N
},
"test": {
"passed": N,
"failed": N,
"ignored": N
},
"build": "OK|NG",
"overall": "OK|NG"
}
Related
/review-all- Full review (includes design compliance and quality)/review-duplicates- Duplicate code detection
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 · 58 lines · 0 tokens per session scan A c44df03cdeaa
check-impl is a command published in the GitHub repository nwiizo/ccswarm (153 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 327 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
rust-test
Rust TDD workflow with unit and property tests.
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.
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.
cargo-target-isolation
Load when: you are about to run (or just ran) a local cargo build/cargo test/cargo run whose result will inform a verdict — a Judge approval or rejection, a Doctor "the fix works", or a Builder "tests pass" before opening a PR.