Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/sandraschi/windows-computer-use-mcp/cursorrulesgit clone --depth 1 https://github.com/sandraschi/windows-computer-use-mcpWhat 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 | $0.00467 | $0.00467 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
cursorrules 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 2d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- cursorrules — 100% identical, 1 lines differ
- cursorrules — 100% identical, 1 lines differ
- cursorrules — 100% identical, 1 lines differ
- cursorrules — 100% identical, 1 lines differ
- cursorrules — 100% identical, 1 lines differ
- cursorrules — 100% identical, 1 lines differ
- cursorrules — 92% identical, 13 lines differ
- cursorrules — 91% identical, 14 lines differ
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)
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, mywienerlinien, 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.
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.
- 2d ago First seen · 63 lines · 467 tokens per session scan A b5afebe8fc37
cursorrules is a cursor rule published in the GitHub repository sandraschi/windows-computer-use-mcp (32 stars, last pushed 15d ago), licensed MIT. It adds 467 tokens to every session, about $0.0023 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-08-30.
Other cursor rules, from other repositories
cursorrules
.rules.
cursorrules
BEFORE making any changes or starting work, ALWAYS.
architect
Global Architect rules for sandraschi's dev environment (Unity, FastMCP, React).
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.