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/onsails/skills/rust-devnpx skills add onsails/skills --skill rust-devgit clone --depth 1 https://github.com/onsails/skillsWhat 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 | $0.00057 | $0.01161 |
| Opus 5 | $0.00028 | $0.00580 |
| Sonnet 5 | $0.00011 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
rust-dev 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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Development
Runtime dispatch
Detect the runtime once, before the workflow:
- Claude Code (
Agent,AskUserQuestion, andSkilltools available) → readruntime-claude.md. - OMP (
taskandasktools available, withskill://…readable throughread) → readskill://rust-dev/runtime-omp.md. - Any other tool surface → stop and report that this skill has no dispatch table for the runtime.
The selected file is a prompt asset, not a role declaration. Its implementation and review labels name the exact runtime subagent arguments. If a named agent is unavailable, stop before delegation: never substitute the generic task or general-purpose agent and never implement delegated work inline.
Workflow
For any non-trivial Rust change:
-
Discover project guidelines — Read
CLAUDE.md,AGENTS.md(in repo root and.claude/,.cursor/,.codex/subdirs),rustfmt.toml,clippy.toml,.clippy.toml,deny.toml, and[workspace.lints]/[lints]sections inCargo.toml. These rules apply in addition to Core Rules below. -
Implement — Delegate through the runtime dispatch table's implementation entry. It rediscovers guidelines, implements, then verifies its own work with
cargo clippy --workspace --tests -- -D warningsandcargo test --workspacebefore reporting done. -
Review — Delegate through the dispatch table's review entry after implementation completes. This is mandatory, not optional. Convert findings into TODOs: critical/warning → fix; suggestions → triage.
-
Fix issues one by one — Delegate each fix through the implementation entry. Do not batch unrelated fixes into one delegation.
-
Final build — Run
cargo build --workspacedirectly.
Core Rules
- Edition 2024: Always
edition = "2024"in Cargo.toml - FAIL FAST: Every error MUST propagate with
?orreturn Err. Logging is NOT handling. See error-handling.md - Dependency versions: Use
x.xformat (e.g.,serde = "1.0"). Find latest withpython3 scripts/check_crate_version.py <crate> - Workspace architecture: Root Cargo.toml defines workspace only. Separate crates for lib/cli/client
- Error types:
thiserror(with backtrace) for libraries,anyhowfor binaries/tests - CLI-first config: Never bypass CLI args. Use
from_cli_args(), neverDefaultthat reads env - No
env::set_varin tests: Pass config through function parameters - Async: Use tokio consistently
- Visibility: Private (default) >
pub(crate)>pub - No magic numbers: Use
constor CLI args
What ships with it
12 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.
- assets/workspace-template/Cargo.toml 471 B
- assets/workspace-template/project-cli/Cargo.toml 413 B
- assets/workspace-template/project-cli/src/main.rs 1.8 KB
- assets/workspace-template/project/Cargo.toml 376 B
- assets/workspace-template/project/src/lib.rs 740 B
- assets/workspace-template/README.md 1.4 KB
- references/dependency-guide.md 1.6 KB
- references/error-handling.md 2.2 KB
- references/module-organization.md 1.4 KB
- runtime-claude.md 416 B
- runtime-omp.md 495 B
- scripts/check_crate_version.py 3.5 KB runs code
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.
- 2d ago First seen · 88 lines · 57 tokens per session scan A 0882bae23b5b
rust-dev is a skill published in the GitHub repository onsails/skills (43 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 1,161 once invoked, about $0.0003 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
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
ai-security
../../../engineering-team/skills/ai-security/SKILL.md.
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
ctf-malware
Provides malware analysis and network traffic techniques for CTF challenges. Use when analyzing obfuscated scripts, malicious packages, custom crypto protocols, C2 traffic, PE/.NET binaries, RC4/AES encrypted communications, YARA rules, shellcode analysis, memory forensics for malware (Volatility malfind, process…