A setup workflow that examines a Rust project and configures checks across nine areas of software quality, including code checks, automated tests, hooks, and continuous integration. Continuous integration means automated checks that run when code changes are submitted.

Setting up linting, formatting, tests, security checks, code-quality checks, Git hooks, and CI for a Rust project.

It helps establish a consistent quality setup while keeping the project's existing configuration, Rust version requirements, and CI jobs.

rust-setup — Skill by ondrasek

Install

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.

agentmods

npx agentmods add skills/ondrasek/cc-plugins/rust-setup

Any agent

npx skills add ondrasek/cc-plugins --skill rust-setup

Clone the repo

git clone --depth 1 https://github.com/ondrasek/cc-plugins

Made for: Claude Code, Codex.

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 718 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00062	$0.00718
Opus 5	$0.00031	$0.00359
Sonnet 5	$0.00012	$0.00144
Haiku 4.5	$0.00006	$0.00072

Measured yesterday against content hash 6f20be7372db, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

The scan reads SKILL.md. This mod also ships 5 executable files (templates/auto-commit.sh, templates/per-edit-fix.sh, templates/quality-gate.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/blueprint/skills/rust-setup/SKILL.md · 70 lines

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 format
skills/shared/references/setup-workflow.md — the 6-phase workflow structure
skills/rust-setup/references/methodology.md — Rust-specific 9 dimensions, thresholds, tool research guidance
skills/rust-setup/references/analysis-checklist.md — what to check in the target codebase
skills/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] sections
clippy.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 pipeline
CLAUDE.md — project instructions
semver-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".

Read the full file on GitHub · 70 lines

Files

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.

Changes

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.

yesterday First seen · 70 lines · 62 tokens per session scan A 6f20be7372db

Subscribe to this mod's changes

rust-setup is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 62 tokens to every session and 718 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.

Git and workflow Security Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens