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-impact)<a href="https://agentmods.dev/commands/plumpslabs/kuma/kuma-impact"><img src="https://agentmods.dev/badge/commands/plumpslabs/kuma/kuma-impact/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-impact"><img src="https://agentmods.dev/badge/commands/plumpslabs/kuma/kuma-impact.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.00016 | $0.00112 |
| Opus 5.5 | $0.00006 | $0.00045 |
| Sonnet 5.5 | $0.00003 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
kuma:impact 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 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.
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:impact
Evaluate blast radius before modifying high-leverage files or shared packages.
kuma_context({ action: "impact", target: "[file or package path]" })
What it returns:
- Direct and transitive consumers
- Downstream affected packages in monorepos
- Mapped test suites to run
- Safety risk level (
low,medium,high,critical)
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 · 17 lines · 16 tokens per session scan A 2e787e9bb27d
kuma:impact is a command published in the GitHub repository plumpslabs/kuma (2 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 112 once invoked, about $0.0001 per session on Opus 5.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
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
arch-boundaries
Install mechanically-enforced architecture boundaries that fail CI on spaghetti imports.
review-change
Review a completed change against its spec in fresh context — evidence-based checks, severity-ranked findings, a written verdict for the human's merge decision.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
test-value-review
Use when a diff adds or changes test files, when a PR claims coverage for config, CI workflows, templates, or HTML output, or when tests look written only to satisfy a "must have tests" rule; not for Playwright selector or performance hygiene (use /playwright-review).
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.