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 skills add andresquirogadev/skillsense --skill rustgit clone --depth 1 https://github.com/andresquirogadev/skillsenseWrote 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/andresquirogadev/skillsense/rust)<a href="https://agentmods.dev/skills/andresquirogadev/skillsense/rust"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/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.00000 | $0.00542 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
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 7d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Skill
You are working on a Rust project. Apply these conventions.
Ownership & Borrowing
- Prefer passing references (
&T/&mut T) over moving values unless ownership transfer is intended. - Use
Cloneexplicitly when you do want a copy — the compiler will tell you when it's needed. - Use
Cow<'_, str>for functions that may return either borrowed or owned string data. - Use
Arc<T>for shared ownership across threads;Rc<T>for single-threaded shared ownership.
Error Handling
- Use
Result<T, E>for recoverable errors; use?to propagate errors up the call stack. - Define domain-specific error types with
thiserror:#[derive(Debug, thiserror::Error)] pub enum AppError { #[error("database error: {0}")] Database(#[from] sqlx::Error), } - Use
anyhow::Resultin application code where detailed error types aren't needed. - Never use
.unwrap()in library or production code — use.expect("descriptive message")during prototyping only.
Types & Traits
- Use
impl Traitin function arguments for ergonomic generics:fn process(items: impl Iterator<Item = u32>). - Implement
Displayfor user-facing types andDebugfor all types (use#[derive(Debug)]). - Use
From/Intofor cheap conversions;TryFrom/TryIntofor fallible ones. - Use
Defaulttrait and#[derive(Default)]where sensible.
Async (Tokio)
- Use
tokio::mainmacro for the async entry point. - Use
tokio::spawnfor fire-and-forget tasks; collect handles to join or detect panics. - Use
tokio::select!for racing multiple async futures. - Use
tokio::sync::Mutex(async-aware) instead ofstd::sync::Mutexin async contexts.
Performance
- Avoid unnecessary heap allocations in hot paths — consider
SmallVecor stack arrays. - Use iterators instead of manual loops — the optimizer handles them well.
- Profile with
cargo flamegraphorperfbefore micro-optimizing.
Clippy & Formatting
- Always run
cargo clippy --all-targets -- -D warningsin CI. - Always run
cargo fmt --checkin CI. - Run
cargo testwithRUST_BACKTRACE=1to get full backtraces on failures.
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.
- 7d ago First seen · 51 lines · 0 tokens per session scan A d99bf97151f0
rust is a skill published in the GitHub repository andresquirogadev/skillsense (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 542 tokens. 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
dcg
Destructive Command Guard - High-performance Rust hook for Claude Code that blocks dangerous commands before execution. SIMD-accelerated, modular pack system, whitelist-first architecture. Essential safety layer for agent workflows.
building-glamorous-tuis
Build terminal UIs with Charmbracelet (Bubble Tea, Lip Gloss, Gum). Use when: Go TUI, shell prompts/spinners, "make CLI prettier", adaptive layouts, async rendering, focus state machines, sparklines, heatmaps, kanban boards, SSH apps.
Complete Rust Development
A comprehensive skill for Rust development that combines error handling, testing, and logging patterns. Demonstrates the 'includes' composition feature by merging content from multiple standalone skills.
Rust Error Handling
Rust-specific error handling patterns, building on the base error handling skill. Demonstrates the 'extends' composition feature.
static-rust
Use for Soma built-in Rust actions, scaffold intent collection, MCP elicitation flows, and CLI/REST action reference.
rust-check
Run cargo check on the current Rust project to find compile errors.