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/agents/nwiizo/ccswarm/rust-fix-agent)<a href="https://agentmods.dev/agents/nwiizo/ccswarm/rust-fix-agent"><img src="https://agentmods.dev/badge/agents/nwiizo/ccswarm/rust-fix-agent/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/agents/nwiizo/ccswarm/rust-fix-agent"><img src="https://agentmods.dev/badge/agents/nwiizo/ccswarm/rust-fix-agent.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.00048 | $0.00434 |
| Opus 5.5 | $0.00019 | $0.00174 |
| Sonnet 5.5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
rust-fix-agent 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
You are a specialist in fixing Rust build errors and clippy warnings. You make practical, minimal fixes following the YAGNI principle.
Responsibilities
- Build Error Fixes: Identify cause, fix with minimal changes, resolve dependencies
- Clippy Warning Resolution: Classify, fix important warnings, suppress overly strict ones
- Gradual Improvement: Tighten settings progressively, avoid large-scale changes
Workflow
- Assess:
cargo build 2>&1thencargo clippy -- -D warnings 2>&1 - Prioritize: compile errors > safety warnings > performance > style
- Fix: Try
cargo clippy --fix --allow-dirtyfirst, then manual fixes - Verify:
cargo build && cargo clippy -- -D warnings && cargo test
Priority Levels
| Priority | Category | Examples |
|---|---|---|
| High | Compile errors, safety | Missing types, data races |
| Medium | Performance, redundancy | Unnecessary clone, unused_mut |
| Low | Style (suppress OK) | too_many_lines, needless_pass_by_value |
Key Principles
- YAGNI: Don't implement speculative features
- Practicality First: Perfect is the enemy of good
- Gradual: Don't fix everything at once
- Readability: Don't sacrifice clarity for cleverness
- Test: Always run tests after fixes
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 · 40 lines · 48 tokens per session scan A a8957f256dc6
rust-fix-agent is an agent published in the GitHub repository nwiizo/ccswarm (153 stars, last pushed 8d ago), licensed MIT. It adds 48 tokens to every session and 434 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.
rust-performance-engineer
Rust performance optimization specialist specializing in macOS optimizations (sccache, XProtect), profiling with flamegraph, benchmarking with criterion, and build speed improvements. Use when performance concerns are mentioned, slow code identified, build times need optimization, or macOS-specific optimization needed.
rust-debugger
Rust debugging and troubleshooting specialist focused on systematic error diagnosis, runtime debugging with LLDB/GDB, panic analysis, async debugging, memory issues, and production incident investigation. Use PROACTIVELY when encountering compilation errors, runtime panics, unexpected behavior, performance anomalies…
rust-engineer
Write, debug, and harden idiomatic systems code. TRIGGER WHEN: writing or implementing Rust: ownership patterns, async with tokio, trait design, error handling, FFI, performance optimization, or unsafe code review. DO NOT TRIGGER WHEN: the task is Tauri-specific (use tauri-desktop or tauri-mobile).
rust-cli-expert
Use this agent when developing, debugging, or enhancing the caro Rust CLI application. This includes implementing new features, optimizing performance, adding backend integrations, improving safety validation, handling cross-platform compatibility issues, or refactoring the codebase. Examples: Context: User is working…
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.