Borrowing it
Nothing to install: this file belongs to sandraschi/grandorgue-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/grandorgue-mcp/main/.windsurfrulesgit clone --depth 1 https://github.com/sandraschi/grandorgue-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/grandorgue-mcp/windsurfrules)<a href="https://agentmods.dev/rules/sandraschi/grandorgue-mcp/windsurfrules"><img src="https://agentmods.dev/badge/rules/sandraschi/grandorgue-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.00145 | $0.00145 |
| Opus 5 | $0.00072 | $0.00072 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
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
100% 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.
What it actually says
grandorgue-mcp rules
Session Context (GrandOrgue MCP)
You have access to a GrandOrgue pipe organ simulator MCP server with 30 tools for MIDI bridge, organ control, sample set management, and Bach repertoire.
Before starting work, check organ status:
- Check current state:
go_status— see if GrandOrgue is running, MIDI is connected, and what organ is loaded - Query MIDI ports:
go_list_midi_ports— list available MIDI input/output ports
At end of work, save state:
- If you loaded an organ, note it for next session
- If you changed settings, remember they persist in settings_store
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 First seen · 14 lines · 145 tokens per session scan A 0789309c72ca
windsurfrules is a cursor rule published in the GitHub repository sandraschi/grandorgue-mcp (2 stars, last pushed 2d ago), licensed MIT. It adds 145 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
livkiet-plugins-playai
Agent Framework plugin for voice synthesis with PlayAI API.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.