Borrowing it
Nothing to install: this file belongs to sandraschi/filesystem-mcp. 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/sandraschi/filesystem-mcp/main/.windsurfrulesgit clone --depth 1 https://github.com/sandraschi/filesystem-mcpWrote 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/sandraschi/filesystem-mcp/windsurfrules)<a href="https://agentmods.dev/rules/sandraschi/filesystem-mcp/windsurfrules"><img src="https://agentmods.dev/badge/rules/sandraschi/filesystem-mcp/windsurfrules.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.1 | $0.00410 | $0.00410 |
| Opus 5 | $0.00205 | $0.00205 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
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 today.
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
Central Documentation Rules
Rule #1: Read Central Docs First
BEFORE making any changes or starting work, ALWAYS:
-
Read the Central Documentation README:
- Location:
D:\Dev\repos\mcp-central-docs\README.md - This shows all important documentation "branches" (folder trees)
- Navigate from there to find specific information
- Location:
-
Follow Documentation Branches:
- Central docs are organized by topic (Anthropic ecosystem, Google ecosystem, patterns, projects, etc.)
- Each branch has its own README explaining what's inside
- Use the branch structure to find relevant docs
-
Check for Existing Patterns:
- Look in
docs/patterns/for design patterns - Check
templates/for reusable templates - Review
docs/projects/for similar project examples
- Look in
-
Avoid Duplication:
- Search existing docs before creating new ones
- Update existing docs rather than creating duplicates
- Reference central docs instead of copying content
Documentation Branches (from Central README)
Quick Reference
Central Docs Location: D:\Dev\repos\mcp-central-docs\
Start Here: D:\Dev\repos\mcp-central-docs\README.md
When in doubt: Read the central README and navigate from there.
Session Context (Filesystem MCP)
You have access to Filesystem MCP: 24 tools for file operations, Docker containers, and system monitoring.
Before starting work:
- Check system status:
monitor_get_system_status(include_processes=False) - Explore relevant directories:
dir_ops(operation="list_directory", path="D:/Dev/repos")
At end of work, clean up:
- Close long-running containers you started, verify locks with
get_lock_status() - Prefer atomic writes through
file_ops(operation="write_file")over raw file APIs
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.
- today First seen · 55 lines · 410 tokens per session scan A f2b4b18bf3af
windsurfrules is a cursor rule published in the GitHub repository sandraschi/filesystem-mcp (6 stars, last pushed today), licensed MIT. It adds 410 tokens to every session, about $0.0020 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-09-06.
Other cursor rules, from other repositories
implementation-honesty
Enforce no fake-success behavior in runtime code and UI.
architect
Global Architect rules for sandraschi's dev environment (Unity and other integrations, FastMCP, React). See mcp-central-docs integrations.
architect
Global Architect rules for sandraschi's dev environment (Unity and other integrations, FastMCP, React). See mcp-central-docs integrations.
architect
Global Architect rules for sandraschi's dev environment (Unity, FastMCP, React).
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
toc-readme
When updating README.md, the table of contents should contain only the second-level headings below it.