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/commands/plumpslabs/matcha/matcha-intensity)<a href="https://agentmods.dev/commands/plumpslabs/matcha/matcha-intensity"><img src="https://agentmods.dev/badge/commands/plumpslabs/matcha/matcha-intensity/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/matcha/matcha-intensity"><img src="https://agentmods.dev/badge/commands/plumpslabs/matcha/matcha-intensity.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.00014 | $0.00279 |
| Opus 5.5 | $0.00006 | $0.00112 |
| Sonnet 5.5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
matcha:intensity 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
/matcha:intensity
Set intensity level for current session.
Usage: /matcha observe|enforce|audit
When to use: at session start or when switching work types — observe for exploration, enforce for normal work (default), audit for critical/high-stakes work.
Checklists
observe — tips only: flag leftover debug statements (e.g. console.log/print/println! via patterns.json)/TODO optionally, syntax check optional.
enforce (default):
- Planning gate: references files, needs evidence, 2+ steps
- Cleanup: remove debug statements, commented code, unused imports
- Verify: syntax ✅, typecheck ✅, tests detected ⚠️
audit (strict):
- Enforce rules + no files >300 lines, all env vars documented
- Verify: syntax ✅, typecheck ✅, lint ✅, tests must exist ✅
Instructions
Persist intensity to .agents/matcha-state.json:
{"intensity": "observe|enforce|audit"}
Confirm with:
🍵 matcha: intensity set to [observe|enforce|audit]
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 · 34 lines · 14 tokens per session scan A 2fb6ff399c60
matcha:intensity is a command published in the GitHub repository plumpslabs/matcha (2 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 279 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-08-31.
Other commands, from other repositories
cochange
Mostra arquivos que tendem a mudar junto com o path especificado, baseado em git history. Use antes de planejar mudanças para evitar PRs incompletos.
provenance
Mostra a cadeia completa de proveniência de um finding - source, commit SHA, age, confidence atual com decay, lifecycle status. Útil para auditar de onde veio uma afirmação na camada compilada.
status
Mostra estado atual da camada .first-plan/ - fase, plano ativo, perguntas abertas, cobertura, confidence, e próxima ação sugerida.
check
Verifica se uma feature específica já existe (em parte ou inteira) no projeto. Antes de planejar, use isto para evitar reimplementação.
why
Consulta a camada compilada para responder "por que X existe?". Argumento pode ser símbolo, path, padrão ou decisão. Cruza topology, conventions, rationale, history.
features
Mostra a matriz de features × status × evidência consolidada em 09-features/INDEX.md. Filtragem por status disponível.