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.
git 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-miri)<a href="https://agentmods.dev/commands/olorehq/olore/cargo-miri"><img src="https://agentmods.dev/badge/commands/olorehq/olore/cargo-miri.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.1 | $0.00000 | $0.00158 |
| Opus 5 | $0.00000 | $0.00079 |
| Sonnet 5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
cargo-miri 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 8d 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-miri(1)
NAME
cargo-miri --- Runs binary crates and tests in Miri
DESCRIPTION
This is an external command distributed with the Rust toolchain as an optional component. It is not built into Cargo, and may require additional installation.
This command is only available on the nightly channel.
For information about usage and installation, see https://github.com/rust-lang/miri.
SEE ALSO
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.
- 8d ago First seen · 23 lines · 0 tokens per session scan A 600e18feee0d
cargo-miri is a command published in the GitHub repository olorehq/olore (103 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 158 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-30.
Other commands, from other repositories
test-rust
Run Rust tests for Solana programs and backend services.
mutation-test
Uses cargo-mutants to run mutation tests and verify test quality.
python-scaffold
Generate a fresh project skeleton, tests and lint config included. TRIGGER WHEN: the user asks to start a new Python project, bootstrap FastAPI/Django/CLI/library structure, or set up uv+pytest+ruff from scratch. DO NOT TRIGGER WHEN: adding to an existing project (use python-engineer).
rust-test
Rust TDD workflow with unit and property tests.
comprehensive-unit-testing-with-pytest
Aims for high test coverage using pytest, testing both common and edge cases.
tokio-test
Generate comprehensive async tests for Tokio applications.