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-publish)<a href="https://agentmods.dev/commands/olorehq/olore/cargo-publish"><img src="https://agentmods.dev/badge/commands/olorehq/olore/cargo-publish.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.04617 |
| Opus 5 | $0.00000 | $0.02308 |
| Sonnet 5 | $0.00000 | $0.00923 |
| Haiku 4.5 | $0.00000 | $0.00462 |
Grade A, and why
cargo-publish 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 How it starts
The opening of the file, as written. The whole thing — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cargo-publish(1)
NAME
cargo-publish --- Upload a package to the registry
SYNOPSIS
cargo publish [options]
DESCRIPTION
This command will create a distributable, compressed .crate file with the
source code of the package in the current directory and upload it to a
registry. The default registry is https://crates.io. This performs the
following steps:
- Performs a few checks, including:
- Checks the
package.publishkey in the manifest for restrictions on which registries you are allowed to publish to.
- Checks the
- Create a
.cratefile by following the steps in cargo-package(1). - Upload the crate to the registry. The server will perform additional checks on the crate.
- The client will poll waiting for the package to appear in the index, and may timeout. In that case, you will need to check for completion manually. This timeout does not affect the upload.
This command requires you to be authenticated using cargo-login(1)
or environment variables of the registry.token
and registries.<name>.token config fields.
See the reference for more details about packaging and publishing.
OPTIONS
Publish 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 · 347 lines · 0 tokens per session scan A e74c90fa869d
cargo-publish 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 4,617 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
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.