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/johnneerdael/multiplatform-cursor-mcp/cursorrulesgit clone --depth 1 https://github.com/johnneerdael/multiplatform-cursor-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.01045 | $0.01045 |
| Opus 5 | $0.00522 | $0.00522 |
| Sonnet 5 | $0.00209 | $0.00209 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade B, and why
cursorrules scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Bash script with sudo - Creates launch agent for auto-start How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Platform Migration Task
Issues Found
-
Windows-specific Path Handling
- Using
process.env.LOCALAPPDATAfor Cursor.exe path - Windows-style path separators in path.join operations
- Hard-coded Windows paths in documentation
- Using
-
Windows-specific Dependencies
node-windowsdependency for window management- Heavy reliance on
node-window-managerfor Windows-specific window operations robotjsfor Windows-specific keyboard/mouse automation
-
Windows-specific APIs
- Windows-specific window handling in WindowsApiService
- Windows-specific process management
- Windows-specific keyboard event handling
Migration Plan
[X] 1. Path Handling - Replace Windows-specific path handling with path.join and process.platform checks - Update documentation with cross-platform examples - Create platform-specific path resolvers
[X] 2. Window Management - Create platform-agnostic window management interface - Implement platform-specific adapters (Windows/MacOS/Linux) - Replace direct Windows API calls with adapter interface
[X] 3. Process Management - Create cross-platform process spawning logic - Handle platform-specific executable paths - Implement platform-specific process detection
[X] 4. Keyboard/Mouse Automation - Create platform-agnostic input automation interface - Replace robotjs with @nut-tree/nut-js - Implement platform-specific input handling
[X] 5. Configuration - Add platform-specific configuration options - Create default configs for each supported platform - Update environment variable handling
Completed Tasks
- Created PathResolver utility for cross-platform path handling
- Created platform-agnostic window management interface
- Implemented Windows and macOS window managers
- Implemented Linux window manager using xdotool
- Created cross-platform input automation service using @nut-tree/nut-js
- Updated CursorInstanceManager to use new abstractions
- Updated documentation with cross-platform instructions
- Added comprehensive test suite for window managers
- Added structured error handling system
- Added logging system with context tracking
- Added tests for input automation service
- Added tests for path resolver
- Created platform-specific installation scripts
- Added integration tests for window management
- Added integration tests for input automation
- Added GitHub Actions workflows for testing and releases
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 · 143 lines · 1,045 tokens per session scan B c59a78beff48
cursorrules is a cursor rule published in the GitHub repository johnneerdael/multiplatform-cursor-mcp (67 stars, last pushed 1y ago), licensed MIT. It adds 1,045 tokens to every session, about $0.0052 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.