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-toggle)<a href="https://agentmods.dev/commands/plumpslabs/matcha/matcha-toggle"><img src="https://agentmods.dev/badge/commands/plumpslabs/matcha/matcha-toggle/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-toggle"><img src="https://agentmods.dev/badge/commands/plumpslabs/matcha/matcha-toggle.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.00012 | $0.00308 |
| Opus 5.5 | $0.00005 | $0.00123 |
| Sonnet 5.5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
matcha:toggle 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:toggle
Toggle matcha governance enforcement on or off for the current workspace.
When to use: when you want to quickly switch between full governance (enforce) and unconstrained exploration (off), or vice versa.
Instructions for agent
- Read
.agents/matcha-state.json. - Check
enabledstatus:- If currently
falseorintensity == "off":- Set
{"enabled": true, "intensity": "enforce"}in.agents/matcha-state.json. - Record audit event to
.agents/audit.log. - Confirm:
🍵 matcha: governance ENABLED - State: 🟢 Active - Mode: enforce - Planning Gate: active - Safety Shield: active
- Set
- If currently
trueor not off:- Set
{"enabled": false, "intensity": "off"}in.agents/matcha-state.json. - Record audit event to
.agents/audit.log. - Confirm:
🍵 matcha: governance PAUSED (off) - State: ⏸ Disabled - Planning Gate: bypassed - Audit Trail: logged to .agents/audit.log - To re-enable: /matcha:on or /matcha:toggle
- Set
- If currently
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 · 36 lines · 12 tokens per session scan A 8804d2085682
matcha:toggle is a command published in the GitHub repository plumpslabs/matcha (2 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 308 once invoked, about $0.0000 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-11.
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.