rust-ci-setup

rust-ci-setup is a skill for Claude Code, Codex from woliveiras/geremmyas. It costs 48 tokens per session (1,264 once invoked), scanned A, original, MIT.

A guide for setting up continuous integration for Rust projects. Continuous integration automatically checks code changes, including formatting, linting, tests, documentation, dependencies, and selected deeper validations.

In plain words
What is it for?
Creating or migrating Rust CI, adding format, Clippy, test, documentation, audit, license, minimum-version, Miri, sanitizer, or fuzzing checks.
Why use it?
It gives a project repeatable checks for every change, helping catch style problems, bugs, build issues, and known security risks before merging.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Creating or migrating Rust CI, adding format, Clippy, test, documentation, audit, license, minimum-version, Miri, sanitizer, or fuzzing checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/woliveiras/geremmyas/rust-ci-setup
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.

Any agent
npx skills add woliveiras/geremmyas --skill rust-ci-setup
Clone the repo
git clone --depth 1 https://github.com/woliveiras/geremmyas

Made for: Claude Code, Codex.

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

agentmods badge for rust-ci-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/woliveiras/geremmyas/rust-ci-setup/github.svg)](https://agentmods.dev/skills/woliveiras/geremmyas/rust-ci-setup)
Your own site
<a href="https://agentmods.dev/skills/woliveiras/geremmyas/rust-ci-setup"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/rust-ci-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.

agentmods 80×15 button for rust-ci-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/woliveiras/geremmyas/rust-ci-setup"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/rust-ci-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,264 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.01264
Opus 5 $0.00024 $0.00632
Sonnet 5 $0.00010 $0.00253
Haiku 4.5 $0.00005 $0.00126

Measured 10d ago against content hash 396a9f432cfa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

rust-ci-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 10d 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.

content/skills/rust-ci-setup/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rust CI Setup

Configure a complete CI pipeline for a Rust project.

When to Use

  • New Rust project needs CI from scratch
  • Adding quality gates (fmt, clippy, test, audit) to an existing project
  • Setting up advanced validation (Miri, sanitizers, fuzzing)
  • Migrating CI to a new provider

Pipeline Layers

Layer 1: Fast Feedback (every PR)

Step Command Purpose
Format cargo fmt --all -- --check Style consistency
Lint cargo clippy --workspace --all-targets --all-features -- -D warnings Code quality
Test cargo nextest run --workspace --all-features (or cargo test) Correctness
Doc cargo doc --workspace --all-features --no-deps Documentation builds

Layer 2: Security & Dependencies (every PR or scheduled)

Step Command Purpose
Audit cargo audit Known vulnerabilities
Deny cargo deny check Licenses, bans, duplicates, advisories
MSRV cargo hack check --rust-version --workspace Minimum supported version

Layer 3: Deep Validation (nightly/scheduled)

Step Command Purpose
Miri cargo +nightly miri test Undefined behavior detection
Sanitizers RUSTFLAGS="-Zsanitizer=address" Memory errors
Fuzzing cargo fuzz run <target> -- -max_total_time=300 Input space exploration
Coverage cargo llvm-cov --workspace --all-features --lcov --output-path lcov.info Code coverage

GitHub Actions Baseline

name: ci

on:
  push:
    branches: [main]
  pull_request:

env:
  CARGO_TERM_COLOR: always
  RUSTFLAGS: "-Dwarnings"

jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install Rust toolchain
        uses: dtolnay/rust-toolchain@stable
        with:
          components: rustfmt, clippy

      - name: Cache Cargo
        uses: actions/cache@v4
        with:
          path: |
            ~/.cargo/registry
            ~/.cargo/git
            target
          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
          restore-keys: ${{ runner.os }}-cargo-

      - name: Format
        run: cargo fmt --all -- --check

      - name: Clippy
        run: cargo clippy --workspace --all-targets --all-features

      - name: Test
        run: cargo test --workspace --all-features

  security:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: dtolnay/rust-toolchain@stable
      - name: Install cargo-deny
        uses: taiki-e/install-action@cargo-deny
      - name: Install cargo-audit
        uses: taiki-e/install-action@cargo-audit
      - run: cargo audit
      - run: cargo deny check

  miri:
    runs-on: ubuntu-latest
    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
    steps:
      - uses: actions/checkout@v4
      - uses: dtolnay/rust-toolchain@nightly
        with:
          components: miri
      - run: cargo +nightly miri test --workspace

Read the full file on GitHub · 179 lines

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.

  1. 10d ago First seen · 179 lines · 48 tokens per session scan A 396a9f432cfa

Subscribe to this mod's changes

rust-ci-setup is a skill published in the GitHub repository woliveiras/geremmyas (10 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,264 once invoked, about $0.0002 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.

Related

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.

ZaxbyHub/opencode-swarm · 60 tokens

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

fusengine/agents · 51 tokens

cargo-workflows

Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.

OutlineDriven/outline-driven-development · 29 tokens

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…

mohitmishra786/low-level-dev-skills · 72 tokens

scaffold-rust-cli

Scaffold a complete Rust CLI project with Cargo, cargo-deny, cargo-nextest, git-cliff, GitHub Actions CI/CD, and Makefile. Use when the user says "scaffold a Rust CLI", "new Rust CLI", "create a Rust binary crate", "start a Rust CLI", "bootstrap a Rust CLI", or starts a Rust command-line tool from scratch. Optionally…

cboone/agent-harness-plugins · 114 tokens

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…

urmzd/dotfiles · 102 tokens