Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/medy-gribkov/arcananpx agentmods add skills/medy-gribkov/arcana/rust-best-practicesWrote 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/medy-gribkov/arcana/rust-best-practices)<a href="https://agentmods.dev/skills/medy-gribkov/arcana/rust-best-practices"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/rust-best-practices/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/medy-gribkov/arcana/rust-best-practices"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/rust-best-practices.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.00080 | $0.02445 |
| Opus 5 | $0.00040 | $0.01222 |
| Sonnet 5 | $0.00016 | $0.00489 |
| Haiku 4.5 | $0.00008 | $0.00245 |
Grade A, and why
rust-best-practices 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 11d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Rust expert specializing in safe, performant, idiomatic Rust for production systems, web services, and CLI tooling.
Use this skill when
- Writing or reviewing Rust code
- Designing ownership/borrowing/lifetime strategies
- Building async services with Tokio
- Structuring cargo workspaces or crate architecture
- Debugging borrow checker or lifetime errors
Ownership, Borrowing, and Lifetimes
The three rules that prevent 90% of borrow checker fights:
- Each value has exactly one owner. When the owner goes out of scope, the value is dropped.
- You can have either ONE mutable reference OR any number of immutable references (not both).
- References must always be valid (no dangling pointers).
// BAD: moving out of a vector element
let names = vec!["alice".to_string(), "bob".to_string()];
let first = names[0]; // ERROR: cannot move out of index
// GOOD: borrow or clone
let first = &names[0]; // borrow
let first = names[0].clone(); // clone if you need ownership
Lifetime annotations - only needed when the compiler can't infer:
// The compiler needs to know: does the return value live as long as `a` or `b`?
fn longest<'a>(a: &'a str, b: &'a str) -> &'a str {
if a.len() > b.len() { a } else { b }
}
// Struct holding a reference MUST declare the lifetime
struct Config<'a> {
name: &'a str,
}
Lifetime scopes visualized:
┌─────────────────────────────────────────┐
│ fn example() { │
│ let owner = String::from("data"); │ ← 'owner lives here
│ ├─────────────────────────┐ │
│ │ let borrowed = &owner; │ │ ← 'borrowed valid
│ │ println!("{borrowed}"); │ │ while owner alive
│ └─────────────────────────┘ │
│ } ← owner dropped, borrowed invalid │
└─────────────────────────────────────────┘
Multiple borrows:
┌─────────────────────────────────────────┐
│ fn multi() { │
│ let mut data = vec![1, 2, 3]; │
│ ├───────────────────┐ │
│ │ let r1 = &data; │ │ ← immutable borrows OK
│ │ let r2 = &data; │ │
│ │ println!("{r1}"); │ │
│ └───────────────────┘ │
│ ├───────────────────┐ │
│ │ let r3 = &mut data; │ │ ← mutable borrow alone
│ │ r3.push(4); │ │
│ └───────────────────┘ │
│ } │
└─────────────────────────────────────────┘
What ships with it
1 file 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.
- 11d ago First seen · 299 lines · 80 tokens per session scan A 099015815a65
rust-best-practices is a skill published in the GitHub repository medy-gribkov/arcana (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 2,445 once invoked, about $0.0004 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
rust-patterns
Rust: ownership, lifetimes, async (Tokio), Result/anyhow/thiserror, traits, unsafe. Triggers: Rust, borrow checker, lifetime, Tokio, cargo, trait, impl, Result, unsafe, clippy.
rust-dependency-audit
Audit Rust dependencies for vulnerabilities, license compliance, supply chain integrity, and freshness using cargo-audit, cargo-deny, cargo-vet.
rust-rules
Rust coding rules: style, patterns, security, testing. Triggers: .rs, Cargo.toml, Cargo.lock, Tokio, Axum, Serde, clippy, cargo test.
desktop-backend-tauri
Tauri 2.x Rust command patterns, state management, error handling, events, channels, testing.
rust-ops
Rust development patterns, ownership, async, error handling, and ecosystem. Use for: rust, cargo, ownership, borrow checker, lifetime, tokio, serde, trait, Result, Option, async rust, crate, derive, impl, enum, pattern matching, Arc, Mutex, Send, Sync, thiserror, anyhow, clap, axum, sqlx, reqwest, rayon, tracing.
rust-sota-arsenal
Reference guide for state-of-the-art Rust tooling across refactoring, profiling, benchmarking, testing, and SIMD optimization. Use whenever the.