rust-patterns

rust-patterns is a skill for Claude Code, Codex from JunMystery/Agent-Guidance-Python. It costs 28 tokens per session (3,271 once invoked), scanned A, a copy of rust-patterns, MIT.

A guide to common Rust patterns for ownership, error handling, traits, generics, concurrency, and async code. It focuses on writing Rust that follows the language's safety and design conventions.

In plain words
What is it for?
Use it when writing, reviewing, or refactoring Rust code, designing modules and crates, or choosing patterns for concurrency and error propagation.
Why use it?
It helps avoid memory and data-race bugs, handle errors consistently, and keep public interfaces and modules easier to maintain.

Skill for Claude CodeCodex

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 skills/junmystery/agent-guidance-python/rust-patterns
Any agent
npx skills add JunMystery/Agent-Guidance-Python --skill rust-patterns
Clone the repo
git clone --depth 1 https://github.com/JunMystery/Agent-Guidance-Python

Made for: Claude Code, Codex.

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-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/rust-patterns.svg)](https://agentmods.dev/skills/junmystery/agent-guidance-python/rust-patterns)
Your own site
<a href="https://agentmods.dev/skills/junmystery/agent-guidance-python/rust-patterns"><img src="https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/rust-patterns.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,271 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% copy Near-identical to another mod 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.00028 $0.03271
Opus 5 $0.00014 $0.01636
Sonnet 5 $0.00006 $0.00654
Haiku 4.5 $0.00003 $0.00327

Measured yesterday against content hash 43612099e89f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rust-patterns 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 yesterday.

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.

Origin

This is a copy

94% identical to rust-patterns — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/rust-patterns/SKILL.md · 501 lines

How it starts

The opening of the file, as written. The whole thing — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rust Development Patterns

Idiomatic Rust patterns and best practices for building safe, performant, and maintainable applications.

When to Use

  • Writing new Rust code
  • Reviewing Rust code
  • Refactoring existing Rust code
  • Designing crate structure and module layout

How It Works

This skill enforces idiomatic Rust conventions across six key areas: ownership and borrowing to prevent data races at compile time, Result/? error propagation with thiserror for libraries and anyhow for applications, enums and exhaustive pattern matching to make illegal states unrepresentable, traits and generics for zero-cost abstraction, safe concurrency via Arc<Mutex<T>>, channels, and async/await, and minimal pub surfaces organized by domain.

Core Principles

1. Ownership and Borrowing

Rust's ownership system prevents data races and memory bugs at compile time.

// Good: Pass references when you don't need ownership
fn process(data: &[u8]) -> usize {
    data.len()
}

// Good: Take ownership only when you need to store or consume
fn store(data: Vec<u8>) -> Record {
    Record { payload: data }
}

// Bad: Cloning unnecessarily to avoid borrow checker
fn process_bad(data: &Vec<u8>) -> usize {
    let cloned = data.clone(); // Wasteful — just borrow
    cloned.len()
}

Use Cow for Flexible Ownership

use std::borrow::Cow;

fn normalize(input: &str) -> Cow<'_, str> {
    if input.contains(' ') {
        Cow::Owned(input.replace(' ', "_"))
    } else {
        Cow::Borrowed(input) // Zero-cost when no mutation needed
    }
}

Error Handling

Use Result and ? — Never unwrap() in Production

// Good: Propagate errors with context
use anyhow::{Context, Result};

fn load_config(path: &str) -> Result<Config> {
    let content = std::fs::read_to_string(path)
        .with_context(|| format!("failed to read config from {path}"))?;
    let config: Config = toml::from_str(&content)
        .with_context(|| format!("failed to parse config from {path}"))?;
    Ok(config)
}

// Bad: Panics on error
fn load_config_bad(path: &str) -> Config {
    let content = std::fs::read_to_string(path).unwrap(); // Panics!
    toml::from_str(&content).unwrap()
}

Read the full file on GitHub · 501 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. yesterday First seen · 501 lines · 28 tokens per session scan A 43612099e89f

Subscribe to this mod's changes

rust-patterns is a skill published in the GitHub repository JunMystery/Agent-Guidance-Python (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 3,271 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to rust-patterns, differing in 5 lines, and is treated as a copy.

Related

Other skills, from other repositories

rust-code-style

Write idiomatic, well-structured Rust for Wassette — single-responsibility design, anyhow error handling, Arc/Mutex for shared state, and the required formatting and linting with cargo +nightly fmt, cargo clippy, and cargo machete. Use when adding or refactoring Rust code in this repository.

microsoft/wassette · 68 tokens

update-keyboard-shortcuts

Audits and synchronizes keyboard shortcuts across docs/keyboardshortcuts.md, crates/regenerator2000-tui/src/ui/dialogkeyboardshortcut.rs, crates/regenerator2000-tui/src/ui/menu.rs, and the view files (viewdisassembly.rs, viewhexdump.rs, viewcharset.rs, viewbitmap.rs, viewblocks.rs, viewsprites.rs).

ricardoquesada/regenerator2000 · 81 tokens

coding

Skill "coding" from ricardoquesada/regenerator2000, covering 6502 disassembler expert skills, core context, technical requirements, 1. 6502 logic and 2. rust performance & safety.

ricardoquesada/regenerator2000 · 0 tokens

cli-architecture

CLI tool design and architecture best practices inspired by Biome, OxcLint, and other modern Rust tools. Use when designing new features, refactoring architecture, or reviewing structural decisions.

ryo-ebata/cc-audit · 41 tokens

rust-best-practices

Rust coding best practices for cc-audit development. Use when writing new Rust code, reviewing code, or refactoring. Covers error handling, safety, performance, and idiomatic patterns.

ryo-ebata/cc-audit · 43 tokens

rust-modern-style

Apply rag-rat's Rust style when writing or reviewing Rust: current stable idioms, module-qualified free functions and constants, explicit persistence contracts, and narrow APIs.

cq27-dev/rag-rat · 37 tokens