Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/matteocervelli/llmsnpx agentmods add skills/matteocervelli/llms/rust-quality-checkerWrote 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/matteocervelli/llms/rust-quality-checker)<a href="https://agentmods.dev/skills/matteocervelli/llms/rust-quality-checker"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/rust-quality-checker/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/matteocervelli/llms/rust-quality-checker"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/rust-quality-checker.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.00038 | $0.03739 |
| Opus 5 | $0.00019 | $0.01869 |
| Sonnet 5 | $0.00008 | $0.00748 |
| Haiku 4.5 | $0.00004 | $0.00374 |
Grade A, and why
rust-quality-checker 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 6d 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 — 798 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Quality Checker Skill
Purpose
This skill provides comprehensive Rust code quality validation including formatting (rustfmt), linting (clippy), compilation checks (cargo check), testing (cargo test), security analysis (cargo audit), and best practices validation. Ensures code meets Rust idioms and project standards.
When to Use
- Validating Rust code quality before commit
- Running pre-commit quality checks
- CI/CD quality gate validation
- Code review preparation
- Ensuring idiomatic Rust code
- Security vulnerability detection
- Performance optimization validation
Quality Check Workflow
1. Environment Setup
Verify Rust Toolchain:
# Check Rust version
rustc --version
# Check Cargo version
cargo --version
# Check rustfmt
rustfmt --version
# Check clippy
cargo clippy --version
Install/Update Components:
# Update Rust toolchain
rustup update
# Install rustfmt (if not present)
rustup component add rustfmt
# Install clippy (if not present)
rustup component add clippy
# Install cargo-audit for security checks
cargo install cargo-audit
# Install cargo-tarpaulin for coverage
cargo install cargo-tarpaulin
Deliverable: Rust toolchain ready
2. Code Formatting Check (rustfmt)
Check Formatting:
# Check if code is formatted
cargo fmt -- --check
# Check with edition
cargo fmt --edition 2021 -- --check
# Check specific files
rustfmt --check src/main.rs
# Check with verbose output
cargo fmt --verbose -- --check
Auto-Format Code:
# Format all code
cargo fmt
# Format with specific edition
cargo fmt --edition 2021
# Format specific file
rustfmt src/main.rs
Configuration (rustfmt.toml):
# rustfmt.toml
edition = "2021"
max_width = 100
hard_tabs = false
tab_spaces = 4
newline_style = "Unix"
use_small_heuristics = "Default"
reorder_imports = true
reorder_modules = true
remove_nested_parens = true
fn_single_line = false
where_single_line = false
imports_granularity = "Crate"
group_imports = "StdExternalCrate"
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.
- 6d ago First seen · 798 lines · 38 tokens per session scan A cca2c97d1ab2
rust-quality-checker is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 3,739 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-09-03.
Other skills, from other repositories
edge-python
Write, run, test and package Edge Python programs with the edge CLI. Use when editing .py files in an Edge Python project or when the user asks for Edge Python code.
cargo-fuzz
Sets up and runs cargo-fuzz, the standard fuzzing tool for Cargo-based Rust projects. Covers cargo fuzz init, the nightly toolchain requirement, fuzztarget! harnesses, Arbitrary-derived structured inputs, sanitizer options, cargo fuzz coverage, and reproducing a crash artifact. Use when fuzzing a Rust crate, writing a…
rust-development
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
cargo-fuzz
Use when initializing, running, measuring coverage, or triaging a cargo-fuzz target in a Rust crate. Not for remote, credential, publish, deploy, or irreversible changes.
presentations
Build PowerPoint (PPTX) decks — pptxgenjs when Node is present, python-pptx when not; edit existing decks in place via OOXML — with visual QA before delivery.
rust-testing-quality
Use when writing, organizing, or running Rust tests — unit, integration, doc-tests, proptest, criterion benchmarks, or cargo-mutants. Not for CI pipeline wiring (rust-tooling-cicd).