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/plumpslabs/kumaWrote 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/plumpslabs/kuma/kuma-studio)<a href="https://agentmods.dev/commands/plumpslabs/kuma/kuma-studio"><img src="https://agentmods.dev/badge/commands/plumpslabs/kuma/kuma-studio/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/plumpslabs/kuma/kuma-studio"><img src="https://agentmods.dev/badge/commands/plumpslabs/kuma/kuma-studio.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.00018 | $0.00115 |
| Opus 5 | $0.00009 | $0.00057 |
| Sonnet 5 | $0.00004 | $0.00023 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
kuma:studio 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.
What it actually says
/kuma:studio
Launch or view Kuma Studio web dashboard.
npx @plumpslabs/kuma studio
Opens http://localhost:3322 featuring:
- Gotcha Shield (status filters & 1-click workaround copy)
- Domain Sequence Flows
- Workspace & Blast Radius Simulator
- Health & Efficiency Metrics
- Calm Knowledge Graph (physics toggle)
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 · 18 lines · 18 tokens per session scan A b22a3e23e69c
kuma:studio is a command published in the GitHub repository plumpslabs/kuma (2 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 115 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-08.
Other commands, from other repositories
gauntlet-loop
Beat a real-world quality bar via builder/critic loops; critics alone decide when each part passes.
decision-audit
Post-build decision ledger and pride gate; audit meaningful choices without changing code until revise.
pathfinder
Map the fog of war before building; separate fixed decisions from open frontiers and unknowns, tag each unknown with a next move, and lay out parallel tracks; plan-only, no execution in the same turn.
scoped-audit
Scoped, plan-first parallel audit of a large surface using capped subagents, with verification before reporting and an approval gate before any change.
tdd
Canon TDD (specify, encode, fulfill) with one test at a time, approval gates, and kitchen-cleaning refactor when needed.
agent-risk-review
One-page agent permission brief before granting access to a system, tool, or account.