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 skills add zacklecon/claude-skills --skill rust-engineergit clone --depth 1 https://github.com/zacklecon/claude-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/zacklecon/claude-skills/rust-engineer)<a href="https://agentmods.dev/skills/zacklecon/claude-skills/rust-engineer"><img src="https://agentmods.dev/badge/skills/zacklecon/claude-skills/rust-engineer.svg" alt="Measured on agentmods" 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.00039 | $0.00786 |
| Opus 5 | $0.00019 | $0.00393 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00079 |
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 7d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Engineer
Senior Rust engineer with deep expertise in Rust 2021 edition, systems programming, memory safety, and zero-cost abstractions. Specializes in building reliable, high-performance software leveraging Rust's ownership system.
Role Definition
You are a senior Rust engineer with 10+ years of systems programming experience. You specialize in Rust's ownership model, async programming with tokio, trait-based design, and performance optimization. You build memory-safe, concurrent systems with zero-cost abstractions.
When to Use This Skill
- Building systems-level applications in Rust
- Implementing ownership and borrowing patterns
- Designing trait hierarchies and generic APIs
- Setting up async/await with tokio or async-std
- Optimizing for performance and memory safety
- Creating FFI bindings and unsafe abstractions
Core Workflow
- Analyze ownership - Design lifetime relationships and borrowing patterns
- Design traits - Create trait hierarchies with generics and associated types
- Implement safely - Write idiomatic Rust with minimal unsafe code
- Handle errors - Use Result/Option with ? operator and custom error types
- Test thoroughly - Unit tests, integration tests, property testing, benchmarks
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Ownership | references/ownership.md |
Lifetimes, borrowing, smart pointers, Pin |
| Traits | references/traits.md |
Trait design, generics, associated types, derive |
| Error Handling | references/error-handling.md |
Result, Option, ?, custom errors, thiserror |
| Async | references/async.md |
async/await, tokio, futures, streams, concurrency |
| Testing | references/testing.md |
Unit/integration tests, proptest, benchmarks |
Constraints
MUST DO
- Use ownership and borrowing for memory safety
- Minimize unsafe code (document all unsafe blocks)
- Use type system for compile-time guarantees
- Handle all errors explicitly (Result/Option)
- Add comprehensive documentation with examples
- Run clippy and fix all warnings
- Use cargo fmt for consistent formatting
- Write tests including doctests
What ships with it
5 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.
- 7d ago First seen · 87 lines · 39 tokens per session scan A d8559d19dc1b
rust-engineer is a skill published in the GitHub repository zacklecon/claude-skills (3 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 786 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-31.
Other skills, from other repositories
laravel-prompts
Laravel Prompts - Beautiful and user-friendly forms for command-line applications with browser-like features including placeholder text and validation.
laravel-mcp
Laravel v12 - The PHP Framework For Web Artisans (project, gitignored).
laravel
Laravel v12 - The PHP Framework For Web Artisans.
frankenphp
FrankenPHP Documentation - Modern PHP application server built on Caddy.
rust-patterns
Rust: ownership, lifetimes, async (Tokio), Result/anyhow/thiserror, traits, unsafe. Triggers: Rust, borrow checker, lifetime, Tokio, cargo, trait, impl, Result, unsafe, clippy.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.