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-setupgit 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-setup)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/rust-setup"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/rust-setup/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-setup"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/rust-setup.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.00062 | $0.00718 |
| Opus 5.5 | $0.00025 | $0.00287 |
| Sonnet 5.5 | $0.00012 | $0.00144 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
rust-setup 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Setup
Critical Rules
- Always present analysis and plan to the user before making changes
- Merge, don't replace — preserve existing Cargo.toml sections, CI jobs, hooks
- Respect the project's Rust edition and MSRV (don't assume latest)
- All hook scripts must be executable (
chmod +x)
Context Files
Read these files before starting:
skills/shared/references/methodology-framework.md— shared principles, hook architecture, exit codes, settings.json formatskills/shared/references/setup-workflow.md— the 6-phase workflow structureskills/rust-setup/references/methodology.md— Rust-specific 9 dimensions, thresholds, tool research guidanceskills/rust-setup/references/analysis-checklist.md— what to check in the target codebaseskills/rust-setup/templates/— annotated examples showing structural patterns. Use templates for patterns but substitute the tools chosen during research.
Workflow
Follow the 6-phase workflow from setup-workflow.md.
Phase 1: Analyze
Follow analysis-checklist.md systematically: Rust edition, MSRV, project structure, targets (WASM, no_std), existing tools, CI, maturity.
Phase 2: Plan
Research tools for each of the 9 dimensions. Rust-specific files to plan:
Cargo.toml—[lints]sectionsclippy.toml,rustfmt.toml,deny.toml.claude/hooks/— quality-gate.sh, per-edit-fix.sh, session-start.sh, optionally auto-commit.sh.claude/settings.json— hook registrations (see methodology-framework.md for format).github/workflows/ci.yml— CI pipelineCLAUDE.md— project instructionssemver-check.sh— only when Dimension 9 is activated at level 3
Present complete plan and wait for approval.
Phase 3: Configure
Read each template in templates/ for the structural pattern, substitute the researched tools. Install required cargo subcommands.
Phase 4: Review
Read references/reviewer-prompt.md for the full prompt template. Spawn reviewer subagent using Task tool with subagent_type: "general-purpose".
What ships with it
13 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.
- references/analysis-checklist.md 7.1 KB
- references/methodology.md 20 KB
- references/reviewer-prompt.md 3.7 KB
- templates/auto-commit.sh 2.8 KB runs code
- templates/ci.yml 3.1 KB
- templates/CLAUDE.md 587 B
- templates/clippy.toml 577 B
- templates/deny.toml 1.4 KB
- templates/per-edit-fix.sh 1.7 KB runs code
- templates/quality-gate.sh 6.6 KB runs code
- templates/rustfmt.toml 163 B
- templates/semver-check.sh 4.0 KB runs code
- templates/session-start.sh 1.5 KB runs code
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 · 70 lines · 62 tokens per session scan A 6f20be7372db
rust-setup is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 62 tokens to every session and 718 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
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.
rust-tooling-cicd
Use when structuring a Cargo workspace or building a Rust CI pipeline — fmt, clippy, cargo-deny/audit, nextest, coverage, MSRV. Not for writing the tests themselves (rust-testing-quality).
cargo-workflows
Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.
cargo-workflows
Cargo workflow skill for Rust projects. Use when managing workspaces, feature flags, build scripts, cargo cache, incremental builds, dependency auditing, or CI configuration with Cargo. Activates on queries about cargo workspaces, Cargo.toml features, build.rs, cargo nextest, cargo deny, cargo check vs build, or…
scaffold-rust-cli
Scaffold a new Rust CLI with Cargo, cargo-deny, cargo-nextest, git-cliff, and CI. Use for "scaffold a Rust CLI" or "new Rust CLI".
scaffold-rust
Scaffold a complete Rust project with CI/CD, release pipeline, and sr.yaml. Uses cargo as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Rust CLI, library, or workspace, or when the user mentions "new Rust project", "cargo init", or…