Borrowing it
Nothing to install: this file belongs to sandraschi/windows-computer-use-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/windows-computer-use-mcp/master/.windsurfrulesgit clone --depth 1 https://github.com/sandraschi/windows-computer-use-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/windows-computer-use-mcp/windsurfrules)<a href="https://agentmods.dev/rules/sandraschi/windows-computer-use-mcp/windsurfrules"><img src="https://agentmods.dev/badge/rules/sandraschi/windows-computer-use-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.
<a href="https://agentmods.dev/rules/sandraschi/windows-computer-use-mcp/windsurfrules"><img src="https://agentmods.dev/badge/rules/sandraschi/windows-computer-use-mcp/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.00585 | $0.00585 |
| Opus 5.5 | $0.00234 | $0.00234 |
| Sonnet 5.5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00059 | $0.00059 |
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 yesterday.
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.
This is a copy
88% identical to cursorrules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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)
Core Standards
STANDARDS.md- Documentation quality standardsSTRUCTURE.md- Directory layout guideCONTRIBUTING.md- How to contribute
Anthropic Ecosystem (docs/anthropic-ecosystem/)
- MCP Protocol, FastMCP, MCPB, Claude Desktop, Glama
Google Ecosystem (docs/google-ecosystem/)
- Gemini 3, Antigravity IDE, Nano Banana Pro, DeepMind, TPU infrastructure
Patterns (docs/patterns/)
- Design patterns for MCP servers and development
Projects (docs/projects/)
- myai, veogen, publictransport-mcp, autohotkey
Monitoring (monitoring/)
- Prometheus/Grafana/Loki stack
Templates (templates/)
- Reusable templates and scripts
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 (windows-computer-use-mcp)
Before starting work: recall this server exposes 18 portmanteau tools
(automation_windows/elements/mouse/keyboard/visual/dialog/shortcut/task/mission/smart/macro/watch,
automation_system, get_desktop_state, get_window_state, approve_automation, automation_safety).
Mutating actions need approve_automation first (or BYPASS_HITL=1 for trusted runs).
At end of work: verify with uv run --no-sync ruff check src/ + pytest, commit per AGENTS.md.
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.
- yesterday Changed · -1 tokens per session 0fcc56c18157
- 16d ago First seen · 71 lines · 586 tokens per session scan A a3129f417d44
windsurfrules is a cursor rule published in the GitHub repository sandraschi/windows-computer-use-mcp (48 stars, last pushed 2d ago), licensed MIT. It adds 585 tokens to every session, about $0.0023 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to cursorrules, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.