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-logoutgit 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-logout)<a href="https://agentmods.dev/commands/olorehq/olore/cargo-logout"><img src="https://agentmods.dev/badge/commands/olorehq/olore/cargo-logout.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.01689 |
| Opus 5 | $0.00000 | $0.00844 |
| Sonnet 5 | $0.00000 | $0.00338 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
cargo-logout 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 6d 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.
This is a copy
78% identical to cargo-add — 258 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cargo-logout(1)
NAME
cargo-logout --- Remove an API token from the registry locally
SYNOPSIS
cargo logout [options]
DESCRIPTION
This command will run a credential provider to remove a saved token.
For the default cargo:token credential provider, credentials are stored
in $CARGO_HOME/credentials.toml where $CARGO_HOME defaults to .cargo
in your home directory.
If a registry has a credential-provider specified, it will be used. Otherwise,
the providers from the config value registry.global-credential-providers will
be attempted, starting from the end of the list.
If --registry is not specified, then the credentials for the default
registry will be removed (configured by
registry.default, which defaults
to https://crates.io/).
This will not revoke the token on the server. If you need to revoke the token, visit the registry website and follow its instructions (see https://crates.io/me to revoke the token for https://crates.io/).
OPTIONS
Logout 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.
- 6d ago First seen · 147 lines · 0 tokens per session scan A 0c00b6ece4f4
cargo-logout 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 1,689 tokens. A static security scan graded it A with 0 findings. It is 78% identical to cargo-add, differing in 258 lines, and is treated as a copy.
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.