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.00792 |
| Opus 5 | $0.00036 | $0.00396 |
| Sonnet 5 | $0.00015 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Development
Use only for Rust crates and Cargo workspaces. Follow the crate's edition, MSRV,
toolchain file, CI, and local style. Rust CLI development (clap, argument
parsing, subcommands) is in scope; apply patterns.md and testing.md — there
is no dedicated CLI reference.
Read First
Read principles.md before writing, changing, or reviewing Rust code. Read conditional references only when the change touches that area.
Conditional References
- patterns.md — crate layout, modules, ownership, traits, errors, async, unsafe, and public APIs.
- testing.md — adding or reshaping Rust tests; keep the local test loop fast.
- linting.md — changing rustfmt, Clippy, cargo check, CI gates, or slow lint workflows.
Comments and Rustdoc
- Use
///or//!rustdoc for public APIs when users need contracts, edge cases, examples, or safety notes. - Add implementation comments only for non-obvious constraints, invariants, side effects, tradeoffs, or unsafe assumptions.
- Keep comments short. Move longer rationale to docs, issue links, or design notes.
- Do not comment obvious code or restate names and types.
- Keep tests readable without comments; add one only for unobvious fixtures, timing, concurrency, unsafe invariants, or regression context.
- Document safety invariants next to
unsafeblocks.
Edition and MSRV
- Inspect
Cargo.toml,Cargo.lock,rust-toolchain.toml, CI, and nearby code before using edition- or version-specific APIs. - Do not use APIs newer than
package.rust-versionor the pinned toolchain unless the task is an upgrade. - Use Edition 2024 syntax only when the crate already opts into
edition = "2024". - Respect feature flags. Do not enable
--all-featuresassumptions in code unless incompatible feature combinations are ruled out.
Verification
Run focused Cargo checks while editing, then the project-configured build, tests, format, and lint before final output. Prefer:
What ships with it
5 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.
- 9d 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 (35 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 792 once invoked, about $0.0004 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
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…
ring:applying-licenses
Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…
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…
cook
Implement an approved spec or focused task through stale-safe source edits. Use this skill when the user says "implement this", "cook this spec", or "fix this bug". Use it for /cook .cheese/specs/ .md. Also use it when the user says "go" or "ship it" with clear acceptance criteria. Run it alone for an unambiguous…
standards
Use this agent when you need to evaluate code, architecture, or development practices against the NASAB framework principles and Rust best practices.