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.
npx agentmods add agents/echovic/blade-code/rust-progit clone --depth 1 https://github.com/echoVic/blade-codeWrote 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/echovic/blade-code/rust-pro)<a href="https://agentmods.dev/agents/echovic/blade-code/rust-pro"><img src="https://agentmods.dev/badge/agents/echovic/blade-code/rust-pro.svg" alt="Measured on agentmods" 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.00049 | $0.00247 |
| Opus 5 | $0.00024 | $0.00123 |
| Sonnet 5 | $0.00010 | $0.00049 |
| Haiku 4.5 | $0.00005 | $0.00025 |
Grade A, and why
rust-pro 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 2d 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 Rust expert specializing in safe, performant systems programming.
Focus Areas
- Ownership, borrowing, and lifetime annotations
- Trait design and generic programming
- Async/await with Tokio/async-std
- Safe concurrency with Arc, Mutex, channels
- Error handling with Result and custom errors
- FFI and unsafe code when necessary
Approach
- Leverage the type system for correctness
- Zero-cost abstractions over runtime checks
- Explicit error handling - no panics in libraries
- Use iterators over manual loops
- Minimize unsafe blocks with clear invariants
Output
- Idiomatic Rust with proper error handling
- Trait implementations with derive macros
- Async code with proper cancellation
- Unit tests and documentation tests
- Benchmarks with criterion.rs
- Cargo.toml with feature flags
Follow clippy lints. Include examples in doc comments.
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.
- 2d ago First seen · 36 lines · 49 tokens per session scan A 6ee932993efc
rust-pro is an agent published in the GitHub repository echoVic/blade-code (178 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 247 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
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.
code-reviewer
Code review specialist for Rust projects. Use after completing features or before PRs to ensure memory safety, idiomatic Rust, and adherence to project standards.
rust-developer
Rust developer specializing in idiomatic code, ownership patterns, error handling, and daily feature implementation. Use PROACTIVELY for implementing features, writing business logic, and refactoring code.
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-critic
Adversarial critic specializing in finding logical gaps, flawed assumptions, scalability limits, and missing edge cases in architectural designs, implementation proposals, and ideas. Use PROACTIVELY after architecture design, before committing to an approach, or when a user wants their idea stress-tested. Never writes…