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 kimgoetzke/coding-agent-configs --skill rust-standardsgit clone --depth 1 https://github.com/kimgoetzke/coding-agent-configsWrote 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/kimgoetzke/coding-agent-configs/rust-standards)<a href="https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/rust-standards"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/rust-standards/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/kimgoetzke/coding-agent-configs/rust-standards"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/rust-standards.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.00017 | $0.00957 |
| Opus 5.5 | $0.00007 | $0.00383 |
| Sonnet 5.5 | $0.00003 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
rust-standards 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 1mo 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
- Unit tests in
#[cfg(test)]modules within each source file - Integration tests in
tests/directory
Naming
- No
get_prefix:fn name()notfn get_name() - Iterator convention:
iter()/iter_mut()/into_iter() - Conversion naming:
as_(cheap &),to_(expensive),into_(ownership) - Static var prefix:
G_CONFIGforstatic, no prefix forconst
Data Types
- Use newtypes:
struct Email(String)for domain semantics - Prefer slice patterns:
if let [first, .., last] = slice - Pre-allocate:
Vec::with_capacity(),String::with_capacity() - Avoid
Vecabuse: use arrays for fixed sizes
Strings
- Prefer
&stroverStringin function parameters - Use
Stringfor ownership: returnStringwhen transferring ownership - Prefer bytes:
s.bytes()overs.chars()when ASCII - Use
Cow<str>when you might need to modify borrowed data - Use
format!over string concatenation with+ - Avoid nested iteration:
contains()on string is O(n*m)
Error Handling
- Use
?for all fallible operations unwrap()in tests only, never productionexpect()only for provably impossible states; the message must justify why it can't fail e.g.expect("regex is valid: validated at compile time")unwrap_or/unwrap_or_else/unwrap_or_defaultfor deliberate fallbacks- Assertions for invariants:
assert!at function entry
Memory
- Meaningful lifetimes:
'src,'ctxnot just'a try_borrow()for RefCell to avoid panic- Shadowing for transformation:
let x = x.parse()?
Concurrency
- Identify lock ordering to prevent deadlocks
- Atomics for primitives, not Mutex for bool/usize
- Choose memory order carefully: Relaxed/Acquire/Release/SeqCst
Async
- Sync for CPU-bound; async is for I/O
- Don't hold locks across await: use scoped guards
Macros
- Avoid unless necessary: prefer functions/generics
- Follow Rust syntax: macro input should look like Rust
Deprecated → Better
lazy_static!→std::sync::OnceLock(since 1.70)once_cell::Lazy→std::sync::LazyLock(since 1.80)std::sync::mpsc→crossbeam::channelonly if you need multi-consumer or better performance under contention;std::sync::mpscis fine for most use casesfailure/error-chain→thiserror/anyhowtry!()→?operator (since 2018)
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.
- 1mo ago First seen · 98 lines · 17 tokens per session scan A e55adb2fc420
rust-standards is a skill published in the GitHub repository kimgoetzke/coding-agent-configs (2 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 957 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
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-development
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
rust-development
You MUST activate this skill when working on Rust projects.
writing-rust
Idiomatic Rust development. Use when writing Rust code, Cargo crates/workspaces, Rust tests, or rustfmt/clippy/cargo workflows. Emphasizes ownership, Result errors, small APIs, stdlib-first dependencies, fast cargo feedback, and behavior tests. NOT for Go, Python, TypeScript, shell scripts, or infra-only work.
rust
Rust engineering standards and deep references — ownership/borrowing-driven design, error handling (thiserror/anyhow), async with tokio, axum services, testing, and clippy/cargo-deny discipline. Load whenever writing, editing, or reviewing Rust: any .rs file, Cargo.toml/Cargo.lock change, cargo or clippy failure, or…
vigilante-issue-implementation-on-rust
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Rust repository with Cargo, Clippy, fmt, and security guidance.