Borrowing it
Nothing to install: this file belongs to imMamdouhaboammar/get-things-done. 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/imMamdouhaboammar/get-things-done/main/.windsurfrulesgit clone --depth 1 https://github.com/imMamdouhaboammar/get-things-doneWrote 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/immamdouhaboammar/get-things-done/windsurfrules)<a href="https://agentmods.dev/rules/immamdouhaboammar/get-things-done/windsurfrules"><img src="https://agentmods.dev/badge/rules/immamdouhaboammar/get-things-done/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/immamdouhaboammar/get-things-done/windsurfrules"><img src="https://agentmods.dev/badge/rules/immamdouhaboammar/get-things-done/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.00538 | $0.00538 |
| Opus 5.5 | $0.00215 | $0.00215 |
| Sonnet 5.5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
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.
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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tools: code-review-graph
This project has a knowledge graph. Start with the code-review-graph MCP tools to narrow scope, then read the source. The graph is cheaper than scanning files and gives you structural context (callers, dependents, test coverage) that file search cannot.
When to use graph tools FIRST
- Exploring code:
semantic_search_nodes_toolorquery_graph_toolinstead of Grep - Understanding impact:
get_impact_radius_toolinstead of manually tracing imports - Code review:
detect_changes_tool+get_review_context_toolinstead of reading entire files - Finding relationships:
query_graph_toolwith callers_of/callees_of/imports_of/tests_for - Architecture questions:
get_architecture_overview_tool+list_communities_tool
Verify in the source
- Narrow scope with the graph, then read the source. Do not change code from graph output alone.
- For any non-trivial change, read the implementation and the relevant tests before concluding.
- Verify the exact source when touching behavior, database logic, migrations, retries, fallbacks, recovery, or compatibility code.
- When the graph and the source disagree, the source wins. The graph may be stale or may not model that relationship.
- An empty graph result can mean "not indexed" or "not statically visible", not "does not exist".
Key Tools
| Tool | Use when |
|---|---|
detect_changes_tool |
Reviewing code changes — gives risk-scored analysis |
get_review_context_tool |
Need source snippets for review — token-efficient |
get_impact_radius_tool |
Understanding blast radius of a change |
get_affected_flows_tool |
Finding which execution paths are impacted |
query_graph_tool |
Tracing callers, callees, imports, tests, dependencies |
semantic_search_nodes_tool |
Finding functions/classes by name or keyword |
get_architecture_overview_tool |
Understanding high-level codebase structure |
refactor_tool |
Planning renames, finding dead code |
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 · 46 lines · 538 tokens per session scan A ee743412a256
windsurfrules is a cursor rule published in the GitHub repository imMamdouhaboammar/get-things-done (2 stars, last pushed 10d ago), licensed MIT. It adds 538 tokens to every session, about $0.0022 per session on Opus 5.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
review-agent-config
Diagnostic gate that checks CLAUDE.md and AGENTS.md for completeness, consistency, and stale artifacts — run right after /cold-start and before /add-feature. Read-only; produces a findings report.
git-pr-reviewer
Pull Request (PR) creation and code review standards with constructive feedback and merge strategies. / TR: Pull Request (PR) oluşturma ve kod inceleme (code review) süreçleri için standartlar ve yapıcı geri bildirim.
code-orchestrator
Main orchestrator managing code architecture, refactoring, clean code principles, and adversarial code reviews. / TR: Kod yazma, güvenlik, eleştirel denetim, test ve mimari süreçlerini yöneten ana orkestratör.
review-gate
Pre-delivery review checklist — run before committing or delivering code.
caveman-review
Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing.
adversarial-code-reviewer
Acts as a senior 'Devil's Advocate' code auditor inspecting showstoppers, memory leaks, unhandled exceptions, and security gaps before code delivery. / TR: Yazılan kodu teslim etmeden önce 'Şeytanın Avukatı' gözüyle gizli bug, showstopper, bellek kaçağı ve mimari açıkları arayan denetçi.