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/wildcard/caroWrote 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/wildcard/caro/caro.release.publish)<a href="https://agentmods.dev/commands/wildcard/caro/caro.release.publish"><img src="https://agentmods.dev/badge/commands/wildcard/caro/caro.release.publish/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/wildcard/caro/caro.release.publish"><img src="https://agentmods.dev/badge/commands/wildcard/caro/caro.release.publish.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.02294 |
| Opus 5 | $0.00005 | $0.01147 |
| Sonnet 5 | $0.00002 | $0.00459 |
| Haiku 4.5 | $0.00001 | $0.00229 |
Grade B, and why
caro.release.publish scanned grade B with 2 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 7d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
- If exit: Display instructions to run command again after approval Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
PUBLISHED_VERSION=$(curl -s https://crates.io/api/v1/crates/caro | jq -r .crate.newest_version) The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 7d ago First seen · 382 lines · 11 tokens per session scan B 67feb580d7dc
caro.release.publish is a command published in the GitHub repository wildcard/caro (37 stars, last pushed today), licensed AGPL-3.0. It adds 11 tokens to every session and 2,294 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks the agent to reveal its instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.
gse-deliver
Merge feature branches, tag release, cleanup. Triggered by /gse:deliver.