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 agentmods add commands/olorehq/olore/cargo-cleangit clone --depth 1 https://github.com/olorehq/oloreWrote 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/commands/olorehq/olore/cargo-clean)<a href="https://agentmods.dev/commands/olorehq/olore/cargo-clean"><img src="https://agentmods.dev/badge/commands/olorehq/olore/cargo-clean.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02984 |
| Opus 5 | $0.00000 | $0.01492 |
| Sonnet 5 | $0.00000 | $0.00597 |
| Haiku 4.5 | $0.00000 | $0.00298 |
Grade A, and why
cargo-clean scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download dependencies before going How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cargo-clean(1)
NAME
cargo-clean --- Remove generated artifacts
SYNOPSIS
cargo clean [options]
DESCRIPTION
Remove artifacts from the target directory that Cargo has generated in the past.
With no options, cargo clean will delete the entire target directory.
OPTIONS
Package Selection
When no packages are selected, all packages and all dependencies in the workspace are cleaned.
Clean Options
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.
- 5d ago First seen · 236 lines · 0 tokens per session scan A 95e7ac076bb1
cargo-clean is a command published in the GitHub repository olorehq/olore (103 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,984 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
new-op
Guide for adding a new variant to the Op enum (e.g. Op::Tag, Op::Link). Covers every place that needs to change.
add
Command "add" from paiml/rust-mcp-sdk, covering cargo pmcp add, usage, subcommands, add server and arguments.
landing
Command "landing" from paiml/rust-mcp-sdk, covering cargo pmcp landing, usage, description, subcommands and landing init.
mutation-test
Uses cargo-mutants to run mutation tests and verify test quality.
rust-review
Lightweight Rust code review using clippy.
rust-features
Get Rust version changelog and new features.