Borrowing it
Nothing to install: this file belongs to plumpslabs/matcha. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/plumpslabs/matcha/main/.windsurfrulesgit 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/windsurfrules)<a href="https://agentmods.dev/rules/plumpslabs/matcha/windsurfrules"><img src="https://agentmods.dev/badge/rules/plumpslabs/matcha/windsurfrules/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/windsurfrules"><img src="https://agentmods.dev/badge/rules/plumpslabs/matcha/windsurfrules.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.00580 | $0.00580 |
| Opus 5.5 | $0.00232 | $0.00232 |
| Sonnet 5.5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
windsurfrules 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.
How it starts
The opening of the file, as written. The whole thing — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🍵 matcha — Windsurf Rules
Core Philosophy
Simple. Efficient. Deliberate. Never twice.
Always Apply
- ⚖️ 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.
- Intent Discovery — Confirm What/Why/How before any code. STOP if Why/How unclear — unless trivial, then proceed on a recorded assumption.
- Reuse Before Write — Search existing code (
file:line). NEVER write what exists. - 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.
- Clean Finish & No Debt Leakage — Done = working AND clean. Mark 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.
Session Memory
- Read
.agents/plan/current.mdat task start (resume after context loss); overwrite it at the planning gate. Append review/audit output to.agents/reports/<agent>-<YYYY-MM>.md(keep latest 5). Lazy-load only.
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 · 580 tokens per session scan A 7450a3a25779
windsurfrules is a cursor rule published in the GitHub repository plumpslabs/matcha (2 stars, last pushed 5d ago), licensed MIT. It adds 580 tokens to every session, about $0.0023 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 cursor rules, from other repositories
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
api-testing
Cypress network interception and API testing patterns (cy.intercept, service mocking, request/response validation).
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
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.