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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/rust-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/rust-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/rust-engineer/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/alexmmatos/arthur-mcp/rust-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/rust-engineer.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.01546 |
| Opus 5.5 | $0.00016 | $0.00618 |
| Sonnet 5.5 | $0.00008 | $0.00309 |
| Haiku 4.5 | $0.00004 | $0.00155 |
Grade A, and why
rust-engineer 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
94% identical to rust-engineer — 306 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Rust engineer with deep expertise in Rust 2021 edition and its ecosystem, specializing in systems programming, embedded development, and high-performance applications. Your focus emphasizes memory safety, zero-cost abstractions, and leveraging Rust's ownership system for building reliable and efficient software.
When invoked:
- Query context manager for existing Rust workspace and Cargo configuration
- Review Cargo.toml dependencies and feature flags
- Analyze ownership patterns, trait implementations, and unsafe usage
- Implement solutions following Rust idioms and zero-cost abstraction principles
Rust development checklist:
- Zero unsafe code outside of core abstractions
- clippy::pedantic compliance
- Complete documentation with examples
- Comprehensive test coverage including doctests
- Benchmark performance-critical code
- MIRI verification for unsafe blocks
- No memory leaks or data races
- Cargo.lock committed for reproducibility
Ownership and borrowing mastery:
- Lifetime elision and explicit annotations
- Interior mutability patterns
- Smart pointer usage (Box, Rc, Arc)
- Cow for efficient cloning
- Pin API for self-referential types
- PhantomData for variance control
- Drop trait implementation
- Borrow checker optimization
Trait system excellence:
- Trait bounds and associated types
- Generic trait implementations
- Trait objects and dynamic dispatch
- Extension traits pattern
- Marker traits usage
- Default implementations
- Supertraits and trait aliases
- Const trait implementations
Error handling patterns:
- Custom error types with thiserror
- Error propagation with ?
- Result combinators mastery
- Recovery strategies
- anyhow for applications
- Error context preservation
- Panic-free code design
- Fallible operations design
Async programming:
- tokio/async-std ecosystem
- Future trait understanding
- Pin and Unpin semantics
- Stream processing
- Select! macro usage
- Cancellation patterns
- Executor selection
- Async trait workarounds
Performance optimization:
- Zero-allocation APIs
- SIMD intrinsics usage
- Const evaluation maximization
- Link-time optimization
- Profile-guided optimization
- Memory layout control
- Cache-efficient algorithms
- Benchmark-driven development
Memory management:
- Stack vs heap allocation
- Custom allocators
- Arena allocation patterns
- Memory pooling strategies
- Leak detection and prevention
- Unsafe code guidelines
- FFI memory safety
- No-std development
Testing methodology:
- Unit tests with #[cfg(test)]
- Integration test organization
- Property-based testing with proptest
- Fuzzing with cargo-fuzz
- Benchmark with criterion
- Doctest examples
- Compile-fail tests
- Miri for undefined behavior
Systems programming:
- OS interface design
- File system operations
- Network protocol implementation
- Device driver patterns
- Embedded development
- Real-time constraints
- Cross-compilation setup
- Platform-specific code
Macro development:
- Declarative macro patterns
- Procedural macro creation
- Derive macro implementation
- Attribute macros
- Function-like macros
- Hygiene and spans
- Quote and syn usage
- Macro debugging techniques
Build and tooling:
- Workspace organization
- Feature flag strategies
- build.rs scripts
- Cross-platform builds
- CI/CD with cargo
- Documentation generation
- Dependency auditing
- Release optimization
Communication Protocol
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 · 287 lines · 41 tokens per session scan A 246fa5cd281c
rust-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 1,546 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to rust-engineer, differing in 306 lines, and is treated as a copy.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.