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/matchaWrote 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/rules/plumpslabs/matcha/kuma)<a href="https://agentmods.dev/rules/plumpslabs/matcha/kuma"><img src="https://agentmods.dev/badge/rules/plumpslabs/matcha/kuma/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/rules/plumpslabs/matcha/kuma"><img src="https://agentmods.dev/badge/rules/plumpslabs/matcha/kuma.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.00434 | $0.00434 |
| Opus 5.5 | $0.00174 | $0.00174 |
| Sonnet 5.5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
kuma 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 MCP tools: kuma_context, kuma_memory, kuma_safety. Record what matters, skip what doesn't.
<kuma_obedience>
🔒 Obedience (non-negotiable)
- MUST call
kuma_context({ action: "init" })at session start. - MUST record gotchas IMMEDIATELY when a bug/quirk is found.
- MUST call
kuma_safety({ action: "verify" })after edits. - MUST NOT call actions outside the 13 core actions. </kuma_obedience>
<kuma_workflow>
🧠 Before coding: kuma_context({ action: "init" })
🔬 Unfamiliar code: kuma_context({ action: "research", scope: "<area>" })
🐛 Found a bug/quirk: kuma_memory({ action: "gotcha" }) (IMMEDIATELY)
🧭 Chose between options: kuma_memory({ action: "decision" })
🔀 Traced a flow: kuma_memory({ action: "arch_flow" }) (max 5 files)
🛡️ Before risky work / after edits: kuma_safety({ action: "guard" | "verify" })
</kuma_workflow>
📖 Full rules: .kuma/init.md
📖 Usage:
• kuma_context({ action: "init" }) — load project context (call first)
• kuma_safety({ action: "guard" }) — safety check before risky ops
• kuma_safety({ action: "verify", scope: "<area>" }) — verify after edits
• .kuma/init.md — full behavioral rules
• .kuma/KNOWN_GOTCHAS.md — gotchas · .kuma/memories/decisions.md — decisions (readable)
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 · 33 lines · 434 tokens per session scan A 4f3cbabc3443
kuma is a cursor rule published in the GitHub repository plumpslabs/matcha (2 stars, last pushed yesterday), licensed MIT. It adds 434 tokens to every session, about $0.0017 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-05.
Other cursor rules, from other repositories
agent-continuity-protocol
Agent continuity protocol - lightweight new-session state check, task ledger, and stale-file prevention for Codex/Cursor/Claude collaboration.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.