Borrowing it
Nothing to install: this file belongs to sachinshelke/codevira. 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/sachinshelke/codevira/main/.windsurfrulesgit clone --depth 1 https://github.com/sachinshelke/codeviraWrote 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/sachinshelke/codevira/windsurfrules)<a href="https://agentmods.dev/rules/sachinshelke/codevira/windsurfrules"><img src="https://agentmods.dev/badge/rules/sachinshelke/codevira/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/sachinshelke/codevira/windsurfrules"><img src="https://agentmods.dev/badge/rules/sachinshelke/codevira/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.01203 | $0.01203 |
| Opus 5.5 | $0.00481 | $0.00481 |
| Sonnet 5.5 | $0.00241 | $0.00241 |
| Haiku 4.5 | $0.00120 | $0.00120 |
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codevira — persistent project memory
This project uses Codevira to give every AI coding tool you use shared memory of the project. Decisions, fix history, the structural code graph, and learned style preferences persist across sessions and across IDEs.
When to call which Codevira tool
Call these MCP tools at the moments the description matches your action — they are fast (tens of ms), token-efficient (summary-by-default), and what makes the project's memory available to you.
At the start of every session
get_session_context()— Always call this first. Returns a ~500-token brief: current focus, recent decisions, top open items. Without it you're blind to the project's history.
Before modifying any file
-
get_impact(file_path)— Returns who calls this code (callers, dependents, blast radius). Required before any rename, signature change, or cross-cutting refactor. If callers > a small number, propose a deprecation+migration plan instead of a direct edit. -
search_decisions(query)— Returns prior architectural decisions touching the topic. Decisions withdo_not_revert: trueMUST be respected; if your proposed change conflicts, surface the decision to the user and wait for approval before proceeding.
Before adopting a pattern, library, or naming convention
search_preferences(category)— Returns this project's coding style (snake_case vs camelCase, error-handling idioms, test layout, etc.). Match these unless the user explicitly asks to change them.
When you fix a bug or land an architectural choice
-
record_decision(...)— Capture the why: what alternatives were considered, why this won, what would force a re-examination. A one-line decision is enough; the value compounds across sessions and across the other AI tools the user opens this project in. -
For commits that fix a bug, prefer commit messages starting with
fix:,bug:,hotfix:, orfixes #N. Codevira scans these into a fix-history database used by the Anti-Regression hero to block silent re-introduction of fixed bugs.
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 · 84 lines · 1,203 tokens per session scan A 09ec00355855
windsurfrules is a cursor rule published in the GitHub repository sachinshelke/codevira (12 stars, last pushed 1mo ago), licensed MIT. It adds 1,203 tokens to every session, about $0.0048 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-12.
Other cursor rules, from other repositories
cursorrules
You are connected to krusch-context-mcp, a persistent working memory engine. You MUST follow this lifecycle protocol across all coding sessions.
replen
Replen integration — session-start matches, portfolio recall, silent auto-reground.
vault-sync
Vault sync protocol — update Obsidian vault after every meaningful action. Inherited by all personas.
error-logging
Error logging protocol — log resolved errors to Known Errors Log for institutional memory. Inherited by all personas.
search-routing
Smart Search Routing — always use QMD semantic search when available, never bypass with grep for vault content.
context-management
Context window management — prevents AI from losing track during long sessions.