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/mutation-test)<a href="https://agentmods.dev/commands/nwiizo/ccswarm/mutation-test"><img src="https://agentmods.dev/badge/commands/nwiizo/ccswarm/mutation-test/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/mutation-test"><img src="https://agentmods.dev/badge/commands/nwiizo/ccswarm/mutation-test.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.00526 |
| Opus 5.5 | $0.00000 | $0.00210 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
mutation-test 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mutation-test - Mutation Test Execution
Uses cargo-mutants to run mutation tests and verify test quality.
Execution Content
- Check if cargo-mutants is installed
- Run mutation tests on specified crate
- Analyze results and report undetected mutants (survivors)
Commands
# Installation check
cargo mutants --version || cargo install cargo-mutants
# List mutants (pre-execution check)
cargo mutants --list -p <crate-name>
# Run mutation tests
cargo mutants -p <crate-name> --timeout 120 -j 4
# Check results
cat mutants.out/caught.txt # Detected mutants
cat mutants.out/missed.txt # Undetected mutants (needs improvement)
cat mutants.out/timeout.txt # Timed out mutants
Result Interpretation
| Result | Meaning | Action |
|---|---|---|
| caught | Tests detected the mutant | Good, no action needed |
| missed | Tests failed to detect the mutant | Tests need to be added |
| timeout | Test execution timed out | Consider adjusting timeout value |
| unviable | Mutant cannot be built | No action needed |
Areas to Focus On
- Functions with many
missedmutants have insufficient test coverage - Prioritize addressing
missedin business logic (usecase/) missedin error handling (error/) is also important
Example Output
317 mutants tested
- 280 caught (88%)
- 20 missed (6%)
- 10 timeout (3%)
- 7 unviable (2%)
Reference
- cargo-mutants documentation
- Mutation testing is a technique for measuring test quality
- "Killing a mutant" = Tests can detect code changes
Execution Steps
Run mutation tests on the ccswarm crate:
# 1. Installation check
cargo mutants --version || cargo install cargo-mutants
# 2. Check mutant list (optional)
cargo mutants --list -p ccswarm | head -50
# 3. Run mutation tests (parallel 4, timeout 120 seconds)
cargo mutants -p ccswarm --timeout 120 -j 4
# 4. Display results summary
echo "=== Caught ===" && wc -l mutants.out/caught.txt
echo "=== Missed ===" && cat mutants.out/missed.txt
echo "=== Timeout ===" && wc -l mutants.out/timeout.txt
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 · 79 lines · 0 tokens per session scan A b15220210445
mutation-test 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 526 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.