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 Nmor/the-claude-council --skill rust-patternsgit clone --depth 1 https://github.com/Nmor/the-claude-councilWrote 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/nmor/the-claude-council/rust-patterns)<a href="https://agentmods.dev/skills/nmor/the-claude-council/rust-patterns"><img src="https://agentmods.dev/badge/skills/nmor/the-claude-council/rust-patterns/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/nmor/the-claude-council/rust-patterns"><img src="https://agentmods.dev/badge/skills/nmor/the-claude-council/rust-patterns.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.00144 | $0.00841 |
| Opus 5.5 | $0.00058 | $0.00336 |
| Sonnet 5.5 | $0.00029 | $0.00168 |
| Haiku 4.5 | $0.00014 | $0.00084 |
Grade A, and why
rust-patterns 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 29d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
6 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.
- 29d ago Changed · -1,337 lines scan C → A 40f5707a1b12
- 1mo ago First seen · 1,380 lines · 144 tokens per session scan C 1ff5b2a7d947
rust-patterns is a skill published in the GitHub repository Nmor/the-claude-council (12 stars, last pushed 27d ago), with no licence file. It adds 144 tokens to every session and 841 once invoked, about $0.0006 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-09-03.
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.
rs-reviewer
Review selected Rust code for ownership, errors, concurrency, async lifecycle, unsafe and FFI contracts, and runtime/API defects using the project's actual toolchain, features, and dependencies.
clean-code-rust
Use when writing or reviewing Rust — deeper idioms (ownership/borrows, error handling with thiserror/anyhow, avoiding unwrap and Rc , iterator style, newtypes).
rust-review
Rust Code Review: Reviews Rust code for ownership patterns, lifetime management, unsafe usage, error handling with Result/Option, concurrency safety, and idiomatic Rust patterns. Covers async Rust (tokio/async-std), trait design, macro hygiene, and performance. Use when the user wants a review of Rust code, mentions…
rust-api-design
Use when designing or reviewing Rust public APIs, trait boundaries, builders, newtypes, typestate transitions, enum versus dyn dispatch, or applying SOLID and creational, structural, or behavioral design patterns without class hierarchies. Triggers include dyn compatibility, dependency injection, API evolution…