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 alexei-led/cc-thingz --skill writing-rustgit clone --depth 1 https://github.com/alexei-led/cc-thingzWrote 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/alexei-led/cc-thingz/writing-rust)<a href="https://agentmods.dev/skills/alexei-led/cc-thingz/writing-rust"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/writing-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/alexei-led/cc-thingz/writing-rust"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/writing-rust.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.00663 |
| Opus 5.5 | $0.00029 | $0.00265 |
| Sonnet 5.5 | $0.00015 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
writing-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 25d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Development
Covers crates, workspaces, and Rust CLIs. Check Cargo.toml, rust-toolchain.toml, and CI before using newer syntax or APIs. Project conventions win over these defaults.
Version and Features
- Stay within
package.rust-version(MSRV) and the pinned toolchain unless the task is an upgrade. - Use Edition 2024 syntax only when the crate sets
edition = "2024". - Keep features additive. Do not assume
--all-featurescompiles when the crate documents mutually exclusive features.
Defaults
- Stdlib and existing crates first.
thiserrorfor library error enums andanyhowfor application glue only when the crate already uses them or boilerplate justifies it. - Newtypes for IDs, tokens, and validated values; enums for states. Private first, then
pub(crate), thenpub. - Implement
From,TryFrom,AsRef,FromStr, andDisplaybefore ad hoc conversion methods. - Parsing and validation return
Resultwith a typed error.unwrap/expectin production code only with a named local invariant. - When the borrow checker objects, fix the data flow before reaching for
clone(). Use lifetimes in APIs only for real zero-copy needs. - Async only where the runtime or I/O boundary requires it. Never hold a blocking mutex guard across
.await. Bound channels, queues, and retries. - Keep secrets out of
Debugoutput, logs, errors, and snapshots. unsafe: small blocks behind a safe API, a// SAFETY:comment stating the invariant, and focused tests or configured Miri.
Checks
Use the project's configured Cargo commands first. While editing, run focused checks (cargo check -p <crate>, cargo test -p <crate> <name>); before finishing, run the full gates:
cargo fmt --check
cargo clippy --all-targets -- -D warnings
cargo test --all-targets # or cargo nextest run, when the project uses nextest
cargo test --doc # --all-targets and nextest both skip doctests
Test behavior through the public API with valid, invalid, and boundary cases, not private helpers. Never run cargo clean as a routine fix; it throws away the incremental cache.
What ships with it
3 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.
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.
- 25d ago Changed · -23 lines 5cf675edd78b
- 1mo ago First seen · 72 lines · 73 tokens per session scan A e54dfa43630a
writing-rust is a skill published in the GitHub repository alexei-led/cc-thingz (38 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 663 once invoked, about $0.0003 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-30.
Other skills, from other repositories
rust-skills
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros…
standards
Use this agent when you need to evaluate code, architecture, or development practices against the NASAB framework principles and Rust best practices.
agent-rust-reviewer
Expert Rust code reviewer specializing in ownership, lifetimes, error handling, unsafe usage, and idiomatic patterns. Use for all Rust code changes. MUST BE USED for Rust projects.
rust-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting Rust code. Detects edition and toolchain from the project. Provides expert critique covering ownership, error handling, unsafe review, async correctness, trait design, type system patterns, performance, SOLID principles, and…
rust-code-review
Review Rust changes on two axes at once — standards (idioms, ownership, errors, API surface, unsafe) and spec (does the change do what was asked) — with a Rust smell baseline layered on the repo lint configuration. Use when reviewing a Rust diff, pull request, or branch, when asked whether a change is ready to merge…
rust-crate-ci
Load before editing any Rust crate in this repo (currently runners/swarm-sandbox-runner). Covers the mandatory local validation gate, common rustfmt/clippy pitfalls, and Windows-specific Rust correctness patterns that CI enforces but are hard to catch locally without a Windows toolchain.