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-init)<a href="https://agentmods.dev/commands/plumpslabs/kuma/kuma-init"><img src="https://agentmods.dev/badge/commands/plumpslabs/kuma/kuma-init/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-init"><img src="https://agentmods.dev/badge/commands/plumpslabs/kuma/kuma-init.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.00101 |
| Opus 5.5 | $0.00007 | $0.00040 |
| Sonnet 5.5 | $0.00004 | $0.00020 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
kuma:init 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:init
Initialize Kuma session context before writing any code.
kuma_context({ action: "init", goal: "[current task goal]" })
What it does:
- Restores cross-session shadow memory
- Loads fresh gotchas for the active branch
- Evaluates repository rules and path constraints
- Informs about branch switches
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 · 18 tokens per session scan A 5596e2a0c3ee
kuma:init is a command published in the GitHub repository plumpslabs/kuma (2 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 101 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
tree
Show the Tau Git Memory tree as a visual schema.
status
Run Tau Git Memory status now.
bm
Ask basemind anything about the current codebase — outlines, refs, callers, git history, blame, diffs, docs, memory.
context-load
Carga de contexto al inicio de sesión. Lee estado del workspace, decisiones recientes, último session save y actividad Git para arrancar con el big picture.
catchup
A command that rebuilds an agent's working context from project notes and recent Git activity.
yolo-abort
Immediate halt of /yolo Hive session mid-action — partial state saved, in-flight git operations rolled back where possible, audit log finalized with abort flag.