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 ondrasek/cc-plugins --skill rust-auditgit clone --depth 1 https://github.com/ondrasek/cc-pluginsWrote 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/ondrasek/cc-plugins/rust-audit)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/rust-audit"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/rust-audit/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/ondrasek/cc-plugins/rust-audit"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/rust-audit.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.00055 | $0.00406 |
| Opus 5.5 | $0.00022 | $0.00162 |
| Sonnet 5.5 | $0.00011 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
rust-audit 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.
What it actually says
Rust Audit
Read-only — does not modify any files.
Context Files
Read these files before starting:
skills/shared/references/audit-workflow.md— the 5-step workflow structureskills/rust-setup/references/methodology.md— the 9 quality dimensions (roles) to audit againstskills/rust-setup/references/analysis-checklist.md— what to check in the target codebase
Workflow
Follow audit-workflow.md. Rust-specific details:
1. Analyze Current State
Detect Rust edition, MSRV, project structure (single crate vs workspace), targets (WASM, no_std). Inventory existing configurations in Cargo.toml [lints], clippy.toml, rustfmt.toml, deny.toml. Check hooks, CI, installed cargo subcommands.
2. Compare Against Methodology
Check each of the 9 dimensions — see methodology.md for Rust-specific tools and thresholds.
3. Check Hook Coverage
Expected hooks: SessionStart (cargo audit + machete), PostToolUse/Edit|Write (cargo fmt), Stop (quality gate), PostToolUse/Bash (semver check).
4. Check CI Coverage
Expected jobs: test, lint, security, deadcode, version, wasm (optional).
5. Report
Present dimension/hook/CI coverage tables with recommendations. Suggest running /blueprint:rust-setup to configure missing dimensions.
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 · 44 lines · 55 tokens per session scan A 645917bd733c
rust-audit is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 406 once invoked, about $0.0002 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
m15-anti-pattern
Use when reviewing code for anti-patterns. Keywords: anti-pattern, common mistake, pitfall, code smell, bad practice, code review, is this an anti-pattern, better way to do this, common mistake to avoid, why is this bad, idiomatic way, beginner mistake, fighting borrow checker, clone everywhere, unwrap in production…
unsafe-checker
A review guide for unsafe Rust code and foreign-function interfaces, which let Rust call code written in languages such as C. It covers raw pointers, memory layout, `extern` functions, safety comments, and undefined behavior.
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…
hexagonal_review
Review a Rust codebase for hexagonal architecture compliance — dependency direction, port shape, adapter grouping, error boundaries, feature-flag placement, and testability. Use when the user asks to review architecture, audit layering, check ports-and-adapters discipline, or evaluate whether a Rust project's…
architectural_review
Review Rust code for advanced architectural patterns — capability mixins, typed commands, concurrency model choice, smart pointer/interior mutability selection, error-handling architecture, and memory layout. Use when the user asks to review system architecture, suggest broad design improvements, or evaluate trait…
rust-review
A Rust code-review skill for services, checking for crashes, unsafe SQL construction, exposed credentials, ignored errors, and unfinished code.