rust-best-practices

rust-best-practices is a skill for Claude Code, Codex from medy-gribkov/arcana. It costs 80 tokens per session (2,445 once invoked), scanned A, original, Apache-2.0.

Guidance for writing safe and idiomatic Rust, a systems programming language with strict compile-time checks. It covers ownership, borrowing, lifetimes, error handling, asynchronous Tokio code, workspaces, web services, command-line tools, and systems programs.

In plain words
What is it for?
Writing or reviewing Rust code, designing ownership and borrowing, building asynchronous services, organising Cargo workspaces, creating web services and command-line tools, and debugging compiler errors.
Why use it?
It helps developers resolve Rust’s ownership and lifetime errors while keeping programs safe and efficient. It also provides patterns for structuring and operating production Rust applications.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is myapp-core = { path = "../core" }.

Good fit Writing or reviewing Rust code, designing ownership and borrowing, building asynchronous services, organising Cargo workspaces, creating web services and command-line tools, and debugging compiler errors.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/medy-gribkov/arcana
agentmods
npx agentmods add skills/medy-gribkov/arcana/rust-best-practices

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin rust-best-practices/plugin install rust-best-practices after adding the marketplace above.

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-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/medy-gribkov/arcana/rust-best-practices/github.svg)](https://agentmods.dev/skills/medy-gribkov/arcana/rust-best-practices)
Your own site
<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.

agentmods 80×15 button for rust-best-practices

Your own site · 80×15
<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>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,445 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 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.1 $0.00080 $0.02445
Opus 5 $0.00040 $0.01222
Sonnet 5 $0.00016 $0.00489
Haiku 4.5 $0.00008 $0.00245

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

Security

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.

skills/rust-best-practices/SKILL.md · 299 lines

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:

  1. Each value has exactly one owner. When the owner goes out of scope, the value is dropped.
  2. You can have either ONE mutable reference OR any number of immutable references (not both).
  3. 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);       │                 │
│   └───────────────────┘                 │
│ }                                       │
└─────────────────────────────────────────┘

Read the full file on GitHub · 299 lines

Files

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.

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. 11d ago First seen · 299 lines · 80 tokens per session scan A 099015815a65

Subscribe to this mod's changes

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.