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/d-oit/rust-2026-template/lint-rustnpx skills add d-oit/rust-2026-template --skill lint-rustgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWhat 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.00063 | $0.00625 |
| Opus 5 | $0.00032 | $0.00313 |
| Sonnet 5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
lint-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 3d 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.
What it actually says
Skill: lint-rust
When to Use
- User asks for this skill's functionality
Purpose
Run comprehensive linting and static analysis on Rust code.
Trigger Conditions
- Before committing code
- During CI/CD pipeline
- When reviewing code quality
- After adding new dependencies
Prerequisites
cargo clippy(bundled with Rust)cargo audit(cargo install cargo-audit)cargo deny(cargo install cargo-deny)cargo machete(cargo install cargo-machete)
Steps
1. Clippy strict mode
cargo clippy --all-targets --all-features -- -D warnings
2. Format check
cargo fmt --all -- --check
3. Security audit
cargo audit
4. Supply chain check
cargo deny check
5. Unused dependencies
cargo machete
Success Criteria
- All clippy lints pass with
-D warnings - Format is consistent
- No known security vulnerabilities
- All licenses are allowed
- No unused dependencies
Related Skills
build-rust- Building the projecttest-rust- Running testsrelease-rust- Release preparation
Rationalizations
| Rationalization | Reality |
|---|---|
| "Clippy passes, so the code is clean." | Clippy alone doesn't check licenses, security, or unused deps. Run the full suite. |
| "cargo audit shows no advisories, we're safe." | Audit only checks known advisories. Also run cargo-deny for license compliance. |
| "I'll skip machete — unused deps aren't a big deal." | Unused deps increase compile time and attack surface. Remove them. |
Red Flags
- Running only
cargo clippywithoutcargo fmt --check - Skipping
cargo auditorcargo denyin CI - Ignoring
-D warningsflag (allows warnings to accumulate)
References
What ships with it
1 file 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.
- 3d ago First seen · 105 lines · 63 tokens per session scan A a328cd6df015
lint-rust is a skill published in the GitHub repository d-oit/rust-2026-template (10 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 625 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-31.
Other skills, from other repositories
next-rspack
Maintain @next/rspack-core and @next/rspack-binding packages. Use when editing rspack/package.json, rspack/crates/binding/Cargo.toml, rspack/rust-toolchain.toml, or packages/next-rspack/package.json. Covers upgrading @rspack/core npm version, rspack crate versions, Rust toolchain version, building and linking for…
code-simplifier
Review RTK Rust code for idiomatic simplification. Detects over-engineering, unnecessary allocations, verbose patterns. Applies Rust idioms without changing behavior.
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
Capsule Development
Build, test, package, install, and debug a current Unicity AOS capsule.
freya
Freya Rust GUI framework best practices, patterns, and conventions. Use when writing Freya components, hooks, elements, or working on a Freya project.
rust-pro
Master modern Rust (2024 edition) with async patterns, advanced type system features, and production-ready systems programming. Expert in the current Rust ecosystem including Tokio, axum, and modern crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.