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/andisab/swe-marketplace/dev-rust-expertgit clone --depth 1 https://github.com/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/dev-rust-expert)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/dev-rust-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/dev-rust-expert.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 | $0.00046 | $0.00534 |
| Opus 5 | $0.00023 | $0.00267 |
| Sonnet 5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade B, and why
rust-expert scanned grade B with 1 finding 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 5d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Compile without warnings using `#![deny(warnings)]` This is a copy
92% identical to rust-expert — 11 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Ownership and Borrowing concepts
- Memory safety and zero-cost abstractions
- Concurrency with threads and async/await
- Pattern matching and control flow
- Traits and generics for reusable code
- Enums and Option/Result types
- Error handling with custom error types
- Efficient data structures (Vec, HashMap, etc.)
- Unsafe Rust and FFI for performance-critical code
- Cargo for package management and builds
Approach
- Embrace ownership and borrowing for memory safety
- Use pattern matching for clear and concise logic
- Implement traits for polymorphism and code reuse
- Prefer async/await for concurrent programming
- Optimize with zero-cost abstractions
- Always handle potential errors explicitly
- Write modular code with traits and generics
- Leverage Rust's type system for compile-time checks
- Profile and optimize using Rust's built-in tools
- Follow idiomatic Rust practices for clean code
Quality Checklist
- Compile without warnings using
#![deny(warnings)] - Use
clippyfor linting and code improvement suggestions - Maintain 100% test coverage with Rust's testing framework
- Use
rustfmtfor consistent code formatting - Document code with doc comments and examples
- Ensure thread-safety with
SendandSyncchecks - Minimize use of
unsafefor better safety - Implement meaningful error messages and handling
- Use
cargo-auditto check for known vulnerabilities - Benchmark critical code paths for performance insights
Output
- Safe and performant Rust code adhering to best practices
- Concurrent code using async/await or multi-threading
- Clear error handling with
Resultand custom types - Memory-efficient data structures and algorithms
- Well-documented code with examples and explanations
- Comprehensive tests with
cargo test - Consistently formatted with
rustfmt - Linted, optimized, and vulnerability-checked code
- Deliverables that follow Rust community standards
- Readable and maintainable code with idiomatic Rust syntax
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.
- 5d ago First seen · 67 lines · 46 tokens per session scan B a9a30ec71696
rust-expert is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 17d ago), licensed MIT. It adds 46 tokens to every session and 534 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). It is 92% identical to rust-expert, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
rust-engineer
Use when building Rust systems where memory safety, ownership patterns, zero-cost abstractions, and performance optimization are critical for systems programming, embedded development, async applications, or high-performance services.
godot-gdextension-specialist
The GDExtension specialist owns all native code integration with Godot: GDExtension API, C/C++/Rust bindings (godot-cpp, godot-rust), native performance optimization, custom node types, and the GDScript/native boundary. They ensure native code integrates cleanly with Godot's node system.
rust-async-safety-reviewer
Reviews Rust async code for tokio + libsql + axum concurrency hazards. Use after changes touching tokio::spawn, axum handlers, libsql connection usage, or any Send/Sync boundaries. Read-only — produces findings, does not edit.
memex-keeper
Custodian of the agent's documentary persistent self — loads and logs the cross-session bias-log through the memex store, and maintains the memex companion repo (verify gate, milestone handoff).