Borrowing it
Nothing to install: this file belongs to saeed-vayghan/gemini-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saeed-vayghan/gemini-agent-skills/master/.gemini/skills/rust-engineer/SKILL.mdgit clone --depth 1 https://github.com/saeed-vayghan/gemini-agent-skillsWrote 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/skills/saeed-vayghan/gemini-agent-skills/rust-engineer)<a href="https://agentmods.dev/skills/saeed-vayghan/gemini-agent-skills/rust-engineer"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/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/skills/saeed-vayghan/gemini-agent-skills/rust-engineer"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/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.00036 | $0.01405 |
| Opus 5 | $0.00018 | $0.00702 |
| Sonnet 5 | $0.00007 | $0.00281 |
| Haiku 4.5 | $0.00004 | $0.00140 |
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.
How it starts
The opening of the file, as written. The whole thing — 268 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 ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 268 lines · 36 tokens per session scan A 7005dee97d17
rust-engineer is a skill published in the GitHub repository saeed-vayghan/gemini-agent-skills (33 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 1,405 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-09-03.
Other skills, from other repositories
makepad-event-action
A guide to handling mouse, keyboard, touch, and lifecycle events in Makepad. It also explains actions, which let a widget communicate an interaction to its parent.
makepad-widgets
Version: makepad-widgets (dev branch) | Last Updated: 2026-01-19 > > Check for updates: https://crates.io/crates/makepad-widgets.
makepad-dsl
A guide to Makepad’s declarative language for defining interface objects and reusable components. It explains properties, prototypes, inheritance, and the live_design syntax used to compose widgets.
makepad-layout
A guide to arranging Makepad interface elements, including their size, spacing, alignment, and flow. Makepad is a Rust toolkit for building user interfaces.
cargo
Cargo Rust package manager and build system. Use for Rust crates.
makepad-skills
Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.