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 rootwarp/claude-code-plugins-monorepo --skill cargo-checkgit clone --depth 1 https://github.com/rootwarp/claude-code-plugins-monorepoWrote 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/rootwarp/claude-code-plugins-monorepo/cargo-check)<a href="https://agentmods.dev/skills/rootwarp/claude-code-plugins-monorepo/cargo-check"><img src="https://agentmods.dev/badge/skills/rootwarp/claude-code-plugins-monorepo/cargo-check/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/rootwarp/claude-code-plugins-monorepo/cargo-check"><img src="https://agentmods.dev/badge/skills/rootwarp/claude-code-plugins-monorepo/cargo-check.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.00000 | $0.00081 |
| Opus 5.5 | $0.00000 | $0.00032 |
| Sonnet 5.5 | $0.00000 | $0.00016 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
cargo-check 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.
What it actually says
/cargo-check
Quickly check Rust code for errors without producing binaries.
Instructions
Run cargo check for fast compilation checking:
cargo check
This is faster than cargo build as it skips code generation.
To check all targets including tests and examples:
cargo check --all-targets
If there are errors, analyze them and suggest fixes.
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 · 22 lines · 0 tokens per session scan A 35c4a5577984
cargo-check is a skill published in the GitHub repository rootwarp/claude-code-plugins-monorepo (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 81 tokens. 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
stack-trace-rust-probe
Internal helper for meta-stack-trace-investigator. Use when a Rust panic or backtrace needs Rust-specific Result/Option checks, cargo test guidance, and patch targets.
rust-tracing
Add or change Rust diagnostic tracing in litellm-rust, including route spans, subscriber layers, and Python logger delivery.
error-handling
Apply error handling and recovery patterns in JavaScript/TypeScript or Node.js. Use when implementing error handling, retry logic, or when the user mentions domain errors, error recovery, error escalation.
cpp-sanitizers
Use in C/C++ projects for crashes, hangs, UB, data races, memory errors. ASan/UBSan/TSan runtime checks. Build sanitizer config separately.
rust-safety
A guide to writing Rust code around ownership, borrowing, error results, and carefully limited unsafe code.
rust-performance
Rust performance workflow: benchmark and profile first, identify hotspots, reduce allocations and contention, improve data layout, tune release profiles, and verify gains with repeatable evidence. Use only after you have a real Rust performance symptom, regression, or hotspot in .rs code.