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/florianbruniaux/ccboard/rust-expertnpx skills add FlorianBruniaux/ccboard --skill rust-expertgit clone --depth 1 https://github.com/FlorianBruniaux/ccboardWrote 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/florianbruniaux/ccboard/rust-expert)<a href="https://agentmods.dev/skills/florianbruniaux/ccboard/rust-expert"><img src="https://agentmods.dev/badge/skills/florianbruniaux/ccboard/rust-expert.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.00045 | $0.01447 |
| Opus 5 | $0.00023 | $0.00724 |
| Sonnet 5 | $0.00009 | $0.00289 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
rust-expert 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 6d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Expert Skill
Expert in idiomatic Rust 1.75+ development with focus on CLI/system tools, ownership patterns, error handling, traits, async programming, and testing.
Core Competencies
1. Ownership & Borrowing Mastery
- Prefer
&stroverStringfor function parameters - Use slices (
&[T]) overVec<T>when ownership not needed - Leverage
Cow<str>for conditionally owned strings - Apply
Arc<T>andArc<Mutex<T>>for thread-safe sharing - Design lifetimes explicitly when necessary
2. Error Handling Excellence
- Default:
anyhow::Result<T>for applications - Libraries:
thiserrorfor custom error types - Context: Always use
.context("operation description")with? - No unwrap: Use
?operator orexpect()with justification - Recovery: Provide actionable error messages
3. Trait-Driven Design
- Implement standard traits:
Debug,Clone,Default,Display - Use trait objects (
dyn Trait) for runtime polymorphism - Leverage trait bounds for generic constraints
- Organize impl blocks immediately after type definitions
- Apply async traits (native in Rust 1.75+)
4. Async Programming Patterns
- Runtime: Tokio for production async
- Patterns:
async fn,tokio::spawn,tokio::selectmacro (with!) - Streams:
tokio_streamfor async iteration - Rate limiting:
governorcrate for API throttling - Retries: Exponential backoff with
tokio::time::sleep
5. CLI Development Best Practices
- Argument parsing:
clapwith derive macros - Config:
serde+toml/yamlfor structured config - Output:
indicatiffor progress,coloredfor styling - Terminal: Handle
SIGINTgracefully, cleanup on exit
6. Testing Strategy
- Embedded tests:
#[cfg(test)] mod tests { use super::*; } - Unit tests alongside code, integration tests in
tests/ - Use
#[should_panic]for expected panics - Mock external dependencies with traits
- Property-based testing with
proptestorquickcheck
What ships with it
11 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.
- anti-patterns/common-mistakes.md 11 KB
- anti-patterns/memory-pitfalls.md 9.8 KB
- checklists/code-review.md 5.5 KB
- checklists/performance.md 7.2 KB
- examples/rtk-patterns.md 8.8 KB
- patterns/async-patterns.md 11 KB
- patterns/cli-patterns.md 11 KB
- patterns/error-handling.md 6.5 KB
- patterns/ownership.md 8.2 KB
- patterns/testing.md 9.7 KB
- patterns/traits-impl.md 9.2 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.
- 6d ago First seen · 174 lines · 45 tokens per session scan A 60ec40f3ccfc
rust-expert is a skill published in the GitHub repository FlorianBruniaux/ccboard (95 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 1,447 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-30.
Other skills, from other repositories
rust
Rust programming patterns and ownership concepts.
rust-systems-programming
Complete guide for Rust systems programming including ownership, borrowing, concurrency, async programming, unsafe code, and performance optimization.
toolchains-rust-core
Core Rust toolchain conventions — ownership/borrowing patterns, error handling, async with tokio, and idiomatic project structure for the rust-engineer agent.
rust
Use when building Axum applications, implementing type-safe handlers, working with SQLx, setting up error handling with thiserror, or writing Rust backend services.
rust
Master production Rust code, lifetimes, and systems programming using a layer-based "meta-cognition" framework. Use whenever writing production Rust code, resolving borrow checker errors (E0382, E0596), designing ownership patterns (Arc, Mutex), or performing crate selection. Do NOT trigger for generic WASM or TS…
Rust Error Handling
Rust-specific error handling patterns, building on the base error handling skill. Demonstrates the 'extends' composition feature.