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 heyAyushh/stacc --skill rustgit clone --depth 1 https://github.com/heyAyushh/staccWrote 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/heyayushh/stacc/rust)<a href="https://agentmods.dev/skills/heyayushh/stacc/rust"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/rust/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/heyayushh/stacc/rust"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/rust.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00967 |
| Opus 5 | $0.00018 | $0.00483 |
| Sonnet 5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Best Practices
Quick Start
Apply these rules by default when touching Rust:
- Organize code by feature/module, not by file type
- Keep structs small and focused; split large data into composable types
- Prefer
Result<T, E>for recoverable errors, avoidpanic! - Document every
unsafeblock with a// SAFETY:rationale - Default to
Vec/HashMap; pre-allocate when size is known - For CLIs, expose non-interactive flags, stdin/file input, actionable errors, and example-rich help
Workflow (use this order)
- Clarify scope: new module, refactor, or review.
- Organize by feature/module; keep type + impls together.
- Ensure error handling uses
Result(avoidpanic!except invariants). - Document
unsafeblocks with// SAFETY:and minimal scope. - Choose data structures intentionally and pre-allocate when size is known.
- For binaries, define the automation contract: flags, stdin, output format, exit codes, and dry-run behavior.
- Add or update tests (unit tests + rustdoc examples for public APIs; CLI help/error tests for binaries).
Review Checklist
- Module layout is feature-driven and cohesive.
Resultused for recoverable errors;panic!justified.- All
unsafeblocks have explicit// SAFETY:rationale. - No oversized structs; data is composed cleanly.
- Collections pre-allocated when size is known.
- CLI surfaces can run unattended and explain retry commands on usage errors.
- Tests and doc examples cover edge cases.
Sub-Skills
Load these for focused guidance on specific topics:
| Skill | When to Use |
|---|---|
ownership |
Ownership/borrow errors (E0382, E0597), lifetime design |
error-handling |
Result vs Option, anyhow vs thiserror, custom error types |
concurrency |
Send/Sync errors, threads vs async, shared state design |
zero-cost-abstractions |
Generics vs dyn Trait, object safety, dispatch choice |
type-driven-design |
Newtypes, type state, PhantomData, invalid states |
performance |
Profiling, allocation reduction, cache, parallelism |
agent-friendly-cli |
Rust binaries, clap command trees, diagnostics/codegen tools |
anti-patterns |
Code review, clone/unwrap overuse, idiomatic rewrites |
coding-guidelines |
Naming, style, modern crate recommendations |
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.
- agent-friendly-cli/SKILL.md 5.5 KB
- anti-patterns/SKILL.md 2.9 KB
- coding-guidelines/SKILL.md 3.0 KB
- concurrency/SKILL.md 3.8 KB
- error-handling/SKILL.md 3.1 KB
- ownership/SKILL.md 3.1 KB
- performance/SKILL.md 2.8 KB
- rust.mdc 9.1 KB
- type-driven-design/SKILL.md 3.2 KB
- zero-cost-abstractions/SKILL.md 3.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.
- 9d ago First seen · 97 lines · 36 tokens per session scan A 564e3a062d64
rust is a skill published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 967 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-09-03.
Other skills, from other repositories
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
omh-rust
This is a Hermes-native rust workflow skill.
bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions…
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.
azure-keyvault-secrets-rust
Client library for Azure Key Vault Secrets — secure storage for passwords, API keys, and other secrets.