rust-engineer

Specialist guidance for building Rust software, especially systems, embedded, asynchronous, and high-performance applications. Rust is a programming language designed to prevent many memory and concurrency errors while keeping programs fast.

In plain words
What is it for?
Use it when designing or changing Rust systems, reviewing ownership and unsafe code, checking dependencies, writing documentation and tests, and validating performance.
Why use it?
It focuses on safe ownership and borrowing, efficient code, reliable concurrency, and checks that help prevent leaks, data races, and other defects.

Agent

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.

agentmods
npx agentmods add agents/vinhnx/vtcode/rust-engineer
Clone the repo
git clone --depth 1 https://github.com/vinhnx/VTCode
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,595 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00041 $0.01595
Opus 5 $0.00020 $0.00797
Sonnet 5 $0.00008 $0.00319
Haiku 4.5 $0.00004 $0.00160

Measured 2d ago against content hash 89e98633b805, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

.vtcode/agents/rust-engineer.md · 315 lines

How it starts

The opening of the file, as written. The whole thing — 315 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. Start with scoped discovery: prefer git diff --name-only, git diff --stat, or advanced code_search; do not scan the whole workspace without a focused query
  3. Review Cargo.toml dependencies and feature flags
  4. Analyze ownership patterns, trait implementations, and unsafe usage
  5. 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 · 315 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. 2d ago First seen · 315 lines · 41 tokens per session scan A 89e98633b805

Subscribe to this mod's changes

rust-engineer is an agent published in the GitHub repository vinhnx/VTCode (825 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,595 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.