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 agentmods add skills/rodolfochicone/rc-project/rc-rustnpx skills add rodolfochicone/rc-project --skill rc-rustgit clone --depth 1 https://github.com/rodolfochicone/rc-projectWrote 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/rodolfochicone/rc-project/rc-rust)<a href="https://agentmods.dev/skills/rodolfochicone/rc-project/rc-rust"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-rust.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.00098 | $0.03203 |
| Opus 5 | $0.00049 | $0.01602 |
| Sonnet 5 | $0.00020 | $0.00641 |
| Haiku 4.5 | $0.00010 | $0.00320 |
Grade A, and why
rc-rust 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 5d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Best Practices
Unified Rust guidelines covering coding style, ownership, error handling, async patterns, traits, testing, performance, linting, and documentation. Apply when writing or reviewing Rust code.
Pair with
This skill owns Rust the language. The stack's layers live elsewhere — reach for them instead of duplicating their guidance here:
rc-axum— HTTP routing, extractors, Tower middleware,IntoResponseerror mapping, WebSocketsrc-sqlx—PgPool, query macros, transactions, migrations,#[sqlx::test]rc-sveltekit— the SSR front end that consumes these APIsrc-code-review— aftercargo fmt/clippy/testcome back green
When to Apply
- Writing new Rust code or designing APIs
- Reviewing or refactoring existing Rust code
- Implementing async systems with Tokio
- Designing error hierarchies with thiserror/anyhow
- Choosing between borrowing, cloning, or ownership transfer
- Setting up tests, benchmarks, or snapshot testing
- Configuring clippy lints and workspace settings
- Optimizing Rust code for performance
Reference Guide
Load detailed guidance based on context. Read the relevant file when the topic arises:
| Topic | Reference | Load When |
|---|---|---|
| Coding Style | references/coding-style.md |
Naming, imports, iterators, comments, string handling, macros |
| Error Handling | references/error-handling.md |
Result, Option, ?, thiserror, anyhow, custom errors, async errors |
| Ownership & Pointers | references/ownership-and-pointers.md |
Lifetimes, borrowing, smart pointers, Pin, Cow, interior mutability |
| Traits & Generics | references/traits-and-generics.md |
Trait design, dispatch, GATs, sealed traits, type state pattern |
| Async & Concurrency | references/async-and-concurrency.md |
Tokio, channels, streams, shutdown, runtime config, async traits |
| Sync Concurrency | references/concurrency-sync.md |
Atomics, Mutex, RwLock, lock ordering, Send/Sync, memory ordering |
| Testing | references/testing.md |
Unit/integration/doc tests, snapshot, proptest, mockall, benchmarks, fuzz |
| Performance | references/performance.md |
Profiling, flamegraph, cloning, stack vs heap, iterators, allocation |
| Clippy & Linting | references/clippy-and-linting.md |
Clippy config, key lints, workspace setup, #[expect] vs #[allow] |
| Documentation | references/documentation.md |
Doc comments, rustdoc, doc lints, coverage checklist |
What ships with it
10 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.
- references/async-and-concurrency.md 10 KB
- references/clippy-and-linting.md 2.9 KB
- references/coding-style.md 5.9 KB
- references/concurrency-sync.md 5.2 KB
- references/documentation.md 4.6 KB
- references/error-handling.md 7.9 KB
- references/ownership-and-pointers.md 7.1 KB
- references/performance.md 3.9 KB
- references/testing.md 8.0 KB
- references/traits-and-generics.md 8.1 KB
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.
- 5d ago First seen · 259 lines · 98 tokens per session scan A 3c7f2ce5b438
rc-rust is a skill published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 29d ago), licensed MIT. It adds 98 tokens to every session and 3,203 once invoked, about $0.0005 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-30.
Other skills, from other repositories
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
stack-trace-rust-probe
Internal helper for meta-stack-trace-investigator. Use when a Rust panic or backtrace needs Rust-specific Result/Option checks, cargo test guidance, and patch targets.
wasm-expert
WebAssembly expert for WASI, component model, Rust/C compilation, and browser integration.
rust-expert
Rust programming expert for ownership, lifetimes, async/await, traits, and unsafe code.
rust-engineer
Acquire expert Rust developer specialisation in rust systems programming, memory safety, and zero-cost abstractions. Masters ownership patterns, async programming, and performance optimisation for mission-critical applications.
rust-agent-handoff
Handoff protocol for the Rust multi-agent development team (rust-architect, rust-developer, rust-testing-engineer, rust-performance-engineer, rust-security-maintenance, rust-code-reviewer, rust-cicd-devops, rust-debugger, rust-critic). Use only when orchestrating subagents via structured YAML files in .local/handoff/.…