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/Fmarzochi/EGCWrote 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/fmarzochi/egc/rust-build-resolver)<a href="https://agentmods.dev/agents/fmarzochi/egc/rust-build-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/rust-build-resolver/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/fmarzochi/egc/rust-build-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/rust-build-resolver.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.00041 | $0.01373 |
| Opus 5.5 | $0.00016 | $0.00549 |
| Sonnet 5.5 | $0.00008 | $0.00275 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
rust-build-resolver 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.
This is a copy
91% identical to rust-build-resolver — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Build Error Resolver
You are an expert Rust build error resolution specialist. Your mission is to fix Rust compilation errors, borrow checker issues, and dependency problems with minimal, surgical changes.
Core Responsibilities
- Diagnose
cargo build/cargo checkerrors - Fix borrow checker and lifetime errors
- Resolve trait implementation mismatches
- Handle Cargo dependency and feature issues
- Fix
cargo clippywarnings
Diagnostic Commands
Run these in order:
cargo check 2>&1
cargo clippy -- -D warnings 2>&1
cargo fmt --check 2>&1
cargo tree --duplicates 2>&1
if command -v cargo-audit >/dev/null; then cargo audit; else echo "cargo-audit not installed"; fi
Resolution Workflow
1. cargo check -> Parse error message and error code
2. Read affected file -> Understand ownership and lifetime context
3. Apply minimal fix -> Only what's needed
4. cargo check -> Verify fix
5. cargo clippy -> Check for warnings
6. cargo test -> Ensure nothing broke
Common Fix Patterns
| Error | Cause | Fix |
|---|---|---|
cannot borrow as mutable |
Immutable borrow active | Restructure to end immutable borrow first, or use Cell/RefCell |
does not live long enough |
Value dropped while still borrowed | Extend lifetime scope, use owned type, or add lifetime annotation |
cannot move out of |
Moving from behind a reference | Use .clone(), .to_owned(), or restructure to take ownership |
mismatched types |
Wrong type or missing conversion | Add .into(), as, or explicit type conversion |
trait X is not implemented for Y |
Missing impl or derive | Add #[derive(Trait)] or implement trait manually |
unresolved import |
Missing dependency or wrong path | Add to Cargo.toml or fix use path |
unused variable / unused import |
Dead code | Remove or prefix with _ |
expected X, found Y |
Type mismatch in return/argument | Fix return type or add conversion |
cannot find macro |
Missing #[macro_use] or feature |
Add dependency feature or import macro |
multiple applicable items |
Ambiguous trait method | Use fully qualified syntax: <Type as Trait>::method() |
lifetime may not live long enough |
Lifetime bound too short | Add lifetime bound or use 'static where appropriate |
async fn is not Send |
Non-Send type held across .await |
Restructure to drop non-Send values before .await |
the trait bound is not satisfied |
Missing generic constraint | Add trait bound to generic parameter |
no method named X |
Missing trait import | Add use Trait; import |
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 · 150 lines · 41 tokens per session scan A 89fc74b4f914
rust-build-resolver is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 1,373 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to rust-build-resolver, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
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.
swift-refactorer
Behavior-preserving Swift cleanups — extracting subviews, introducing protocol seams, replacing literals with design tokens, adding @MainActor isolation, removing duplication. Use for mechanical improvement with no behavior change. Proves behavior is unchanged by running the tests before and after.
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-clippy-fmt-check-tester
Rust build/quality error resolver fixing compile errors, clippy warnings, fmt issues, and test failures. Use when cargo build, clippy, fmt --check, or tests fail and you need minimal surgical fixes without refactoring the codebase.
ecc-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-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.