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/spec-kitty.dashboard)<a href="https://agentmods.dev/commands/wildcard/caro/spec-kitty.dashboard"><img src="https://agentmods.dev/badge/commands/wildcard/caro/spec-kitty.dashboard/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/spec-kitty.dashboard"><img src="https://agentmods.dev/badge/commands/wildcard/caro/spec-kitty.dashboard.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.00009 | $0.01234 |
| Opus 5.5 | $0.00004 | $0.00494 |
| Sonnet 5.5 | $0.00002 | $0.00247 |
| Haiku 4.5 | $0.00001 | $0.00123 |
Grade A, and why
spec-kitty.dashboard 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 1mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( 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.
- 1mo ago First seen · 175 lines · 9 tokens per session scan A b2170b243eec
spec-kitty.dashboard is a command published in the GitHub repository wildcard/caro (40 stars, last pushed today), licensed AGPL-3.0. It adds 9 tokens to every session and 1,234 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
jira-issue-use-playwright
Like /jira-issue-use-browser, but pinned to the Playwright MCP — use for a clean automated browser (public page or test credentials, no real session needed). Example — /jira-issue-use-playwright "Composer > Save" saving toasts failure but the record persists.
cep-wizard
Launch a local, localhost-only browser wizard for a project with ult-repo-layout installed (initialized or not) — guides an uninitialized or not-yet-discovered repo through Run Discover, then shows resolved layer/slot state through four labeled boxes and a directory picker, and lets you resolve pending layout…
jira-issue-use-browser
Same as /jira-issue, plus a live-browser deep-dive using whatever browser MCP is connected (Chrome, Playwright, or Cypress): reproduce as the signed-in user, watch network + console, capture the failing request/response, mock to isolate, and record a repro before filing the Jira issue. Example …
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.
sugar-task
Create a comprehensive Sugar task with rich context and metadata.
standup
Alias of /board — the async sprint snapshot.