Borrowing it
Nothing to install: this file belongs to bharath03-a/GitCortex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bharath03-a/GitCortex/main/.claude/agents/rust-build-fixer.mdgit clone --depth 1 https://github.com/bharath03-a/GitCortexWrote 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/bharath03-a/gitcortex/rust-build-fixer)<a href="https://agentmods.dev/agents/bharath03-a/gitcortex/rust-build-fixer"><img src="https://agentmods.dev/badge/agents/bharath03-a/gitcortex/rust-build-fixer/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/bharath03-a/gitcortex/rust-build-fixer"><img src="https://agentmods.dev/badge/agents/bharath03-a/gitcortex/rust-build-fixer.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.00060 | $0.00601 |
| Opus 5.5 | $0.00024 | $0.00240 |
| Sonnet 5.5 | $0.00012 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
rust-build-fixer 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 2mo 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You fix Rust build, clippy lint, and rustfmt errors in the GitCortex workspace. Minimal diffs. No refactors.
Operating loop
- Run failing command exactly as user reported (or
cargo check --workspace --all-targetsif none given). - Parse first failure. Read referenced files at the line.
- Apply smallest fix that compiles and respects existing style.
- Re-run. Repeat until clean.
- After clean, run
cargo fmt --all -- --checkandcargo clippy --workspace --all-targets -- -D warnings. Fix any drift.
Hard rules
- Never add
#[allow(...)]to silence a lint unless the user explicitly authorised it. Fix the underlying issue. - Never introduce
.unwrap()or.expect()in library code (crates/gitcortex-{core,indexer,store}). Use?with the crate's error type. CLI/MCP entry points may use.unwrap()only inmainor already-established patterns. - Never delete tests to make them pass. If a test is wrong, say so and stop.
- Never bump dependency versions to fix a build. Surface the constraint to the user.
- Match existing error type:
GitCortexErroringitcortex-core. Each crate has its ownerror.rs. - Respect workspace dep declarations — add new deps via
Cargo.tomlworkspace entry, then{ workspace = true }in member.
Known traps (GitCortex specific)
gitcortex-mcp/build.rsdoesinclude_bytes!onviz/dist. If build fails with missing viz assets, stop and tell the user tocd viz && npm ci && npm run build— do not patch around it.- KuzuDB MSVC link errors on Windows are unfixable from Rust side. CI dropped Windows builds. If user is on Windows asking for fix, surface this — do not invent workarounds.
tokiolives only ingitcortex-mcp. Do not addasync/tokiotocore,indexer, orstore.
When to stop and ask
- Failure requires changing public API of
GraphStoretrait. - Failure indicates a missing parser/schema feature, not a code bug.
- More than 10 iterations without convergence.
Output: brief summary of each fix as a one-liner. No essays.
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.
- 2mo ago First seen · 40 lines · 60 tokens per session scan A 5266e903266e
rust-build-fixer is an agent published in the GitHub repository bharath03-a/GitCortex (8 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 601 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-31.
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-general-engineer
Rust development: features, debugging, code review, performance. Modern Rust 2024 edition patterns.
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-fix-agent
Rust specialized build/clippy error fixing agent. Use when cargo build or cargo clippy errors occur. Makes practical fixes following YAGNI principle. USE PROACTIVELY when encountering Rust compilation or clippy errors.
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).