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-yank)<a href="https://agentmods.dev/commands/olorehq/olore/cargo-yank"><img src="https://agentmods.dev/badge/commands/olorehq/olore/cargo-yank.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.02876 |
| Opus 5 | $0.00000 | $0.01438 |
| Sonnet 5 | $0.00000 | $0.00575 |
| Haiku 4.5 | $0.00000 | $0.00288 |
Grade A, and why
cargo-yank 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cargo-yank(1)
NAME
cargo-yank --- Remove a pushed crate from the index
SYNOPSIS
cargo yank [options] crate@version
cargo yank [options] --version version [crate]
DESCRIPTION
The yank command removes a previously published crate's version from the server's index. This command does not delete any data, and the crate will still be available for download via the registry's download link.
Cargo will not use a yanked version for any new project or checkout without a pre-existing lockfile, and will generate an error if there are no longer any compatible versions for your crate.
This command requires you to be authenticated with either the --token option
or using cargo-login(1).
If the crate name is not specified, it will use the package name from the current directory.
How yank works
For example, the foo crate published version 1.5.0 and another crate bar
declared a dependency on version foo = "1.5". Now foo releases a new, but
not semver compatible, version 2.0.0, and finds a critical issue with 1.5.0.
If 1.5.0 is yanked, no new project or checkout without an existing lockfile
will be able to use crate bar as it relies on 1.5.
In this case, the maintainers of foo should first publish a semver compatible
version such as 1.5.1 prior to yanking 1.5.0 so that bar and all projects
that depend on bar will continue to work.
As another example, consider a crate bar with published versions 1.5.0,
1.5.1, 1.5.2, 2.0.0 and 3.0.0. The following table identifies the
versions cargo could use in the absence of a lockfile for different SemVer
requirements, following a given release being yanked:
| Yanked Version / SemVer requirement | bar = "1.5.0" |
bar = "=1.5.0" |
bar = "2.0.0" |
|---|---|---|---|
1.5.0 |
Use either 1.5.1 or 1.5.2 |
Return Error | Use 2.0.0 |
1.5.1 |
Use either 1.5.0 or 1.5.2 |
Use 1.5.0 |
Use 2.0.0 |
2.0.0 |
Use either 1.5.0, 1.5.1 or 1.5.2 |
Use 1.5.0 |
Return Error |
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 · 222 lines · 0 tokens per session scan A 7c15d9053f3b
cargo-yank 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,876 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
crate-info
Get information about a Rust crate including latest version, features, and changelog.
rust-features
Get Rust version changelog and new features.
release
Prepare and execute a Python package release with verification steps.
changelog
Create UPCOMINGCHANGELOG.md from the structured changelog input below. If UPCOMINGCHANGELOG.md already exists, ignore its current contents completely. Do not preserve, merge, or reuse text from the existing file.
ts-package
Prepare TypeScript library for npm publishing with proper declarations and dual package support.
rel
You are tasked with releasing a Ruby gem. Follow these steps in order.