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/wildcard/caro/caro.featuregit 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.feature)<a href="https://agentmods.dev/commands/wildcard/caro/caro.feature"><img src="https://agentmods.dev/badge/commands/wildcard/caro/caro.feature.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.00020 | $0.03575 |
| Opus 5 | $0.00010 | $0.01788 |
| Sonnet 5 | $0.00004 | $0.00715 |
| Haiku 4.5 | $0.00002 | $0.00358 |
Grade A, and why
caro.feature 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 4d 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.
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.
- 4d ago First seen · 573 lines · 20 tokens per session scan A 9972a9293540
caro.feature is a command published in the GitHub repository wildcard/caro (37 stars, last pushed yesterday), licensed AGPL-3.0. It adds 20 tokens to every session and 3,575 once invoked, about $0.0001 per session on Opus 5. 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-09-01.
Other commands, from other repositories
design-plan
Generate a concrete design system (tokens, style, type, UX) before building UI.
design-review
Run the 7-phase design review (WCAG AA, responsive, interaction) on a page or URL.
check
Checks if the code is ready to be committed.
fixme
Looks for all the fixme comments in the code and attempts to fix them.
test-multiline
Command with multiline prompt.
autospec.implement
Execute the implementation plan by processing tasks defined in tasks.yaml.