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.
npx agentmods add instructions/plumpslabs/matcha/gemini-mdgit 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/instructions/plumpslabs/matcha/gemini-md)<a href="https://agentmods.dev/instructions/plumpslabs/matcha/gemini-md"><img src="https://agentmods.dev/badge/instructions/plumpslabs/matcha/gemini-md.svg" alt="Measured on agentmods" 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 | $0.00654 | $0.00654 |
| Opus 5 | $0.00327 | $0.00327 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
matcha GEMINI.md 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🍵 matcha — Antigravity CLI Convention
This project uses the matcha engineering philosophy.
Simple. Efficient. Deliberate. Never twice.
Core Rules
- ⚖️ Proportionality (effort ↔ risk) — Match ceremony to task size. Trivial (≤5 LOC, 1 file, no logic): minimal plan, fast pass. Small (1-3 files): short plan + light review. Large (cross-cutting/prod risk): full gate. Planning > implementation = over-planning. Exit conditions beat STOP — proceed on a recorded assumption rather than blocking on trivia.
- Purpose First (Intent Discovery) — Before any code, confirm What/Why/How. Evidence required. Stop if Why/How unclear — unless trivial, then proceed on a recorded assumption.
- Reuse Before Write — Search existing code (
file:line). Never duplicate. - Type-Safe & Boundary Guard — Strict types (no
any). Validate inputs/schemas at entry points. - Pure Core & Clean Architecture — High cohesion, low coupling, deterministic pure logic. Isolate side effects.
- Performance & Resource Awareness — Zero N+1/unbatched IO, avoid O(n²+) time/space complexity, prevent memory leaks, limit payload sizes (pagination/stream).
- Security & Data Safety — Parameterize queries (no SQLi/XSS), env vars (
APPNAME_VAR_NAME), restrict least-privilege state access. - Resilience & Explicit Errors — Idempotent retry-safe mutations, explicit error paths, no silent catches or dummy fallbacks.
- Zero Tech Debt Leakage — Mark deliberate shortcuts with
// matcha: [reason]at write time — a comment documenting a deliberate choice (skip/workaround/intentional hardcode) gets the prefix while writing; plain "what this does" comments need none. - Loop Guardrail (Self-Termination) — Halt & ask for guidance if 2 consecutive attempts fail or repeat.
- Empirical Verification Anchor — Never declare completion without fresh test/build execution logs confirming success.
Intensity
- observe — tips only
- enforce — full checkpoints (default)
- audit — enforce + mandatory cleanup
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.
- 3d ago First seen · 44 lines · 654 tokens per session scan A 472ed1c4505a
matcha GEMINI.md is an instructions file published in the GitHub repository plumpslabs/matcha (1 stars, last pushed 23d ago), licensed MIT. It adds 654 tokens to every session, about $0.0033 per session on Opus 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 instructions, from other repositories
assaio AGENTS.md
Instructions for assaio/assaio, covering agents.md — assaio, what this is, code philosophy (non-negotiable), code standards (enforced + human-reviewed) and honesty rules (product-critical).
jcodemunch-mcp AGENTS.md
AGENTS.md instructions for jgravelle/jcodemunch-mcp, covering code exploration policy, session-aware routing and model-driven tool tiering.
agent-toolkit AGENTS.md
Instructions for Arnosdeus/agent-toolkit, covering shared agent instructions, repository inspection, existing architecture, frontend and ui quality and testing.
skillr CLAUDE.md
Instructions for eooo-io/skillr, covering claude.md, project direction, repo layout, tech stack (cli) and dev workflow.
syncai copilot-instructions.md
Instructions for dmtrkzntsv/syncai, covering claude.md, build & run, architecture, lifecycle and identify is the routing decision.
m2ui-skill copilot-instructions.md
Copilot instructions for martysama0134/m2ui-skill, covering m2ui — metin2 ui code generator, mode detection, reference documentation, two ui styles and critical code generation rules.