rust-engineer

rust-engineer is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 41 tokens per session (1,546 once invoked), scanned A, a copy of rust-engineer, MIT.

A Rust development agent for building reliable, efficient software with the Rust programming language. It focuses on Rust's ownership and borrowing rules, memory safety, embedded systems, asynchronous applications, and high-performance services.

In plain words
What is it for?
Use it to review Cargo projects, improve ownership and lifetime code, assess unsafe sections, write tests and documentation, and optimize or benchmark Rust software.
Why use it?
It helps prevent memory leaks and data races while keeping performance-sensitive code efficient. It also helps developers work through Rust's strict rules and project tooling.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Use it to review Cargo projects, improve ownership and lifetime code, assess unsafe sections, write tests and documentation, and optimize or benchmark Rust software.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/rust-engineer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for rust-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/rust-engineer/github.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/rust-engineer)
Your own site
<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.

agentmods 80×15 button for rust-engineer

Your own site · 80×15
<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>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,546 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.01546
Opus 5 $0.00020 $0.00773
Sonnet 5 $0.00008 $0.00309
Haiku 4.5 $0.00004 $0.00155

Measured 6d ago against content hash 246fa5cd281c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 6d 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.

Origin

This is a copy

94% identical to rust-engineer — 66 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.

.claude/agents/rust-engineer.md · 287 lines

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:

  1. Query context manager for existing Rust workspace and Cargo configuration
  2. Review Cargo.toml dependencies and feature flags
  3. Analyze ownership patterns, trait implementations, and unsafe usage
  4. 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

Read the full file on GitHub · 287 lines

Changes

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.

  1. 6d ago First seen · 287 lines · 41 tokens per session scan A 246fa5cd281c

Subscribe to this mod's changes

rust-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,546 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to rust-engineer, differing in 66 lines, and is treated as a copy.