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-generate-lockfile)<a href="https://agentmods.dev/commands/olorehq/olore/cargo-generate-lockfile"><img src="https://agentmods.dev/badge/commands/olorehq/olore/cargo-generate-lockfile.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.02304 |
| Opus 5 | $0.00000 | $0.01152 |
| Sonnet 5 | $0.00000 | $0.00461 |
| Haiku 4.5 | $0.00000 | $0.00230 |
Grade A, and why
cargo-generate-lockfile 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 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.
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 This is a copy
80% identical to cargo-add — 229 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cargo-generate-lockfile(1)
NAME
cargo-generate-lockfile --- Generate the lockfile for a package
SYNOPSIS
cargo generate-lockfile [options]
DESCRIPTION
This command will create the Cargo.lock lockfile for the current package or
workspace. If the lockfile already exists, it will be rebuilt with the latest
available version of every package.
See also cargo-update(1) which is also capable of creating a Cargo.lock
lockfile and has more options for controlling update behavior.
OPTIONS
Display 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.
- 8d ago First seen · 178 lines · 0 tokens per session scan A 564f7cd6a2b5
cargo-generate-lockfile 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,304 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 80% identical to cargo-add, differing in 229 lines, and is treated as a copy.
Other commands, from other repositories
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.
review
Comprehensive code review for blz changes.
generate-docs
Generates a Rust-scoped symbol inventory to assist agents in understanding the public API surface of the workspace.
profile-performance
Profile Julia code to find performance bottlenecks — CPU hot spots, runtime dispatch, GC pressure, allocations, and type instabilities — using a fully headless (no-GUI) workflow.