filesystem-mcp: Cursor rule for Windsurf

.windsurfrules

windsurfrules is a cursor rule for Windsurf from sandraschi/filesystem-mcp. It costs 410 tokens per session, scanned A, original, MIT.

Rules requiring an agent to read a central documentation repository before making changes. They also direct it to find existing patterns, templates, and related projects before creating new documentation or code.

In plain words
What is it for?
Use them when starting repository changes, researching project conventions, or adding documentation.
Why use it?
They reduce duplicated work and help changes follow existing project guidance. They also make the required documentation sources clear before work begins.

Cursor rule for Windsurf

Written for Windsurf: a Windsurf rule.

This is sandraschi/filesystem-mcp's own configuration. It tells Windsurf how to work on filesystem-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything filesystem-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/sandraschi/filesystem-mcp/main/.windsurfrules
Clone the repo
git clone --depth 1 https://github.com/sandraschi/filesystem-mcp

Made for: Windsurf.

Wrote 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.

agentmods badge for windsurfrules

README.md
[![agentmods](https://agentmods.dev/badge/rules/sandraschi/filesystem-mcp/windsurfrules/github.svg)](https://agentmods.dev/rules/sandraschi/filesystem-mcp/windsurfrules)
Your own site
<a href="https://agentmods.dev/rules/sandraschi/filesystem-mcp/windsurfrules"><img src="https://agentmods.dev/badge/rules/sandraschi/filesystem-mcp/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.

agentmods 80×15 button for windsurfrules

Your own site · 80×15
<a href="https://agentmods.dev/rules/sandraschi/filesystem-mcp/windsurfrules"><img src="https://agentmods.dev/badge/rules/sandraschi/filesystem-mcp/windsurfrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 410 This file is loaded in full into every session.
When invoked 410 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00410 $0.00410
Opus 5.5 $0.00164 $0.00164
Sonnet 5.5 $0.00082 $0.00082
Haiku 4.5 $0.00041 $0.00041

Measured 2mo ago against content hash f2b4b18bf3af, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.windsurfrules · 55 lines

What it actually says

Central Documentation Rules

Rule #1: Read Central Docs First

BEFORE making any changes or starting work, ALWAYS:

  1. 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
  2. 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
  3. Check for Existing Patterns:

    • Look in docs/patterns/ for design patterns
    • Check templates/ for reusable templates
    • Review docs/projects/ for similar project examples
  4. 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:

  1. Check system status: monitor_get_system_status(include_processes=False)
  2. 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
Changes

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.

  1. 2mo ago First seen · 55 lines · 410 tokens per session scan A f2b4b18bf3af

Subscribe to this mod's changes

windsurfrules is a cursor rule published in the GitHub repository sandraschi/filesystem-mcp (7 stars, last pushed 7d ago), licensed MIT. It adds 410 tokens to every session, about $0.0016 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-06.

Related

windsurfrules compared with cursor rules from other repositories

windsurfrules next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
windsurfrulessandraschi/filesystem-mcpCursor rule77d agoMITA410Windsurf
implementation-honestysandraschi/virtualization-mcpCursor rule19todayMITA114Cursor
architectsandraschi/blender-mcpCursor rule658d agoMITC1,153Cursor
architectsandraschi/virtualization-mcpCursor rule19todayMITC1,196Cursor
architectsandraschi/plexmcpCursor rule28d agoMITC811Cursor
about-codebaselineai-intelligence/lineai-mcp-serverCursor rule3711d agoMPL-2.0A13Cursor
validate-design-earlyRethunk-AI/clodbridgeCursor rule04mo agoMITA227Cursor