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 fusengine/agents --skill rust-tooling-cicdgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/rust-tooling-cicd)<a href="https://agentmods.dev/skills/fusengine/agents/rust-tooling-cicd"><img src="https://agentmods.dev/badge/skills/fusengine/agents/rust-tooling-cicd/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/fusengine/agents/rust-tooling-cicd"><img src="https://agentmods.dev/badge/skills/fusengine/agents/rust-tooling-cicd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01348 |
| Opus 5.5 | $0.00020 | $0.00539 |
| Sonnet 5.5 | $0.00010 | $0.00270 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
rust-tooling-cicd 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 22d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
It also covers supply-chain policy as code — committing deny.toml, centralizing dependency versions in [workspace.dependencies] rather than pinning per member — and auxiliary tooling like cargo hack (feature-powerset checks) and cargo machete (unused-dependency pruning).
Out of scope: writing the tests themselves (unit/integration/proptest/criterion) belongs to rust-testing-quality; non-Rust CI pipelines are not covered.
Rust Tooling & CI/CD
Agent Workflow (MANDATORY)
Before ANY tooling/CI work, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Inspect existing
Cargo.toml, workspace layout,.github/workflows - fuse-ai-pilot:research-expert - Verify current cargo / cargo-deny / nextest docs via Context7/Exa
- mcp__context7__query-docs - Check workspace-inheritance and feature-unification specifics
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
| Layer | Tool(s) | Purpose |
|---|---|---|
| Layout | Cargo workspaces | One Cargo.lock, one target/, shared metadata |
| Config | features, workspace.dependencies |
Optional functionality, single source of versions |
| Format/lint | cargo fmt, cargo clippy |
Style + correctness lints, warnings as errors |
| Supply chain | cargo deny, cargo audit |
Licenses, bans, duplicate/yanked/vulnerable crates |
| Test | cargo nextest, cargo test --doc |
Fast parallel run + doc-tests |
| Coverage/MSRV | cargo llvm-cov, cargo hack |
Line coverage, minimum-supported-Rust matrix |
Critical Rules
- Gate order is fixed - fmt → clippy → deny → audit → nextest →
test --doc→ coverage. Cheap, fast-failing checks run first. -D warningson clippy in CI -cargo clippy --all-targets --all-features -- -D warnings. A warning must fail the build.- Commit
deny.toml- supply-chain policy is code; it must be reviewed and versioned. - Centralize versions in
workspace.dependencies- members inherit withdep.workspace = true; never pin the same crate twice. cargo test --docis a separate step - nextest never runs doc-tests (see rust-testing-quality).
What ships with it
5 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.
- 22d ago Changed 5863c802c72b
- 1mo ago Changed 4f9379c5a219
- 1mo ago First seen · 142 lines · 51 tokens per session scan A e50f3be10ad5
rust-tooling-cicd is a skill published in the GitHub repository fusengine/agents (33 stars, last pushed 7d ago), licensed MIT. It adds 51 tokens to every session and 1,348 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-09-03.
Other skills, from other repositories
polars
High-performance DataFrame library for Python ETL, analytics, and pandas migration. It supports expression-based data manipulation with lazy query optimization, parallel execution, streaming out-of-core processing, Arrow interoperability, and optional GPU execution.
pinocchio-development
Comprehensive guide for building high-performance Solana programs using Pinocchio - the zero-dependency, zero-copy framework. Covers account validation, CPI patterns, optimization techniques, and migration from Anchor.
setup-rust-ci
Write a GitHub Actions workflow for a Rust repo — format, clippy at the configured level, tests, and an MSRV job, derived from the posture the repo already recorded.
building-telegram-bots
Writes correct, version-aware Telegram bot code. Use when writing, extending, or debugging a Telegram bot in python-telegram-bot, aiogram, grammY, or Telegraf. Not for Telegram client API (TDLib), languages other than Python and Node.js, or non-Telegram platforms.
pennylane
Builds and differentiates PennyLane quantum circuits, hybrid PyTorch or JAX models, molecular VQE and QAOA workflows. Use for variational quantum algorithms, quantum machine learning, simulator validation, and moving validated circuits to provider plugins. For hardware-specific compilation use qiskit or cirq; for…
architect
Design the idiomatic Elixir architecture for a rewrite: set the compatibility bar (ADR-000), consult phx specialists on open questions, then build contexts, ledger and ADRs. Use after /rewrite:analyze.