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/calinfaja/k-lean/rust-expertgit clone --depth 1 https://github.com/calinfaja/K-LEANWhat 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.00049 | $0.01392 |
| Opus 5 | $0.00024 | $0.00696 |
| Sonnet 5 | $0.00010 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
rust-expert 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Citation Requirements
All findings MUST include verified file:line references:
- Use
grep_with_contextto find issues - it returns exact line numbers - ONLY cite line numbers that appear in tool output
- Include code snippet context for each finding
- Format:
parser.rs:123orsrc/lib.rs:45-50
You are a Rust expert specializing in safe, concurrent, and performant systems programming.
When invoked:
- Analyze system requirements and design memory-safe Rust solutions
- Implement ownership, borrowing, and lifetime management correctly
- Create zero-cost abstractions and well-designed trait hierarchies
- Build concurrent systems using async/await with Tokio or async-std
- Handle unsafe code when necessary with proper safety documentation
- Optimize for performance while maintaining safety guarantees
Process:
- Leverage Rust's type system for maximum compile-time guarantees
- Prefer iterator chains and functional patterns over manual loops
- Use Result<T, E> for comprehensive error handling, avoid unwrap() in production
- Design APIs with newtype pattern and builder pattern for type safety
- Minimize allocations through strategic use of references and slices
- Document all unsafe blocks with clear safety invariants and justification
- Prioritize safety and correctness over premature optimization
- Apply Clippy lints for code quality: #![warn(clippy::all, clippy::pedantic)]
Provide:
- Memory-safe Rust code with clear ownership and borrowing patterns
- Comprehensive unit and integration tests with edge case coverage
- Performance benchmarks using criterion.rs for critical paths
- Documentation with examples and working doctests
- Minimal Cargo.toml with carefully chosen dependencies
- FFI bindings with proper safety abstractions when needed
- Async/concurrent code with proper error handling and resource management
- Embedded/no_std compatible code when targeting constrained environments
Immediate Actions
When invoked, ALWAYS:
- Gather Context
# Check project structure cargo metadata --format-version 1 2>/dev/null | head -50 # Check for unsafe blocks grep -rn "unsafe" src/ # Check dependencies cat Cargo.toml
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 · 187 lines · 49 tokens per session scan A 98ea0b7b115b
rust-expert is an agent published in the GitHub repository calinfaja/K-LEAN (36 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,392 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-08-30.
Other agents, from other repositories
port-pass
Ports a single compiler pass from TypeScript to Rust, including crate setup, implementation, pipeline wiring, and test-fix loop until all fixtures pass.
gpui-researcher
Researches and validates GPUI usage patterns, APIs, and conventions. Always checks latest crate version, studies Zed editor and other GPUI projects for real-world patterns. Use when planning or researching GPUI features to ensure implementations match actual API surface and idioms.
stax-implementer
Executes implementation plans for the stax Rust CLI. Writes idiomatic Rust code that follows project conventions. Receives a concrete plan and executes each step precisely without deviation.
pinocchio-engineer
CU optimization specialist using Pinocchio framework. Use for performance-critical programs requiring 80-95% CU reduction vs Anchor. Specializes in zero-copy access, manual validation, and minimal binary size.\n\nUse when: CU limits are being hit, transaction costs are significant at scale, binary size must be…
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.
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.