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.
git clone --depth 1 https://github.com/JOHNNYMACONNY/mighty-routerWrote 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/johnnymaconny/mighty-router/windsurfrules)<a href="https://agentmods.dev/rules/johnnymaconny/mighty-router/windsurfrules"><img src="https://agentmods.dev/badge/rules/johnnymaconny/mighty-router/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/johnnymaconny/mighty-router/windsurfrules"><img src="https://agentmods.dev/badge/rules/johnnymaconny/mighty-router/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.00742 | $0.00742 |
| Opus 5.5 | $0.00297 | $0.00297 |
| Sonnet 5.5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mighty Router — Cursor AI Configuration
You are running with the Mighty Router rules enabled. Before proceeding with any code modification, research, or audit, you must classify the request and apply the corresponding execution profile rules.
1. Automatic Escalation Rules
Regardless of self-classification, you MUST use the MIGHTY-FORENSIC profile if the task involves modifying any files or directories matching project-specific or default high-risk paths.
Dynamic Configuration
Check if .mightyrc or .mighty.json exists in the workspace root. If it does:
- Read the file and locate the
high_risk_pathsarray. - If any file about to be modified matches any pattern or folder name in
high_risk_paths, automatically escalate the task to the MIGHTY-FORENSIC profile.
Fallback/Default Paths
If no project-specific configuration is found, automatically escalate if any target path matches:
/gateway/or/transports//persistence/,/db/, or database schemasSOUL.mdor core agent instructions/prompts- Security-critical settings or credentials
2. Profile Selection
Classify the task into exactly ONE of the following profiles:
[Profile 1] MIGHTY-LIGHT
- Use Case: General queries, explanations, code walkthroughs, or simple questions.
- Rules:
- Do not use XML tags.
- Keep responses brief, direct, and telegraphic.
- Do not run commands or modify files.
[Profile 2] MIGHTY-VERIFY
- Use Case: Verification tasks, UAT checks, checking if tests passed, auditing logs/artifacts.
- Rules:
- Verify expected artifacts exist on disk (do not assume).
- Differentiate clearly between: Passed / Failed / Not Checked / Not Provable.
- Present a concise bulleted summary of checked evidence. Do not modify files.
[Profile 3] MIGHTY-STANDARD
- Use Case: Routine, low-risk code edits, refactors, or new minor files.
- Rules:
- No XML tags (to save output tokens).
- Check first: Verify target files exist and read them before editing.
- Plan: State a 1-3 sentence plan in plain text.
- Act: Apply changes using the minimum necessary edit footprint.
- Verify: Run tests or compile the code to confirm success.
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 · 61 lines · 742 tokens per session scan A 0bf3c08be70e
windsurfrules is a cursor rule published in the GitHub repository JOHNNYMACONNY/mighty-router (1 stars, last pushed 1mo ago), licensed MIT. It adds 742 tokens to every session, about $0.0030 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
alembic-migrations
To add a non-nullable column and set a specific value for all existing rows without a persistent server default.
shell-scripts
Shell Scripts.
token-the-ripper
Strip scaffolding. Keep signal.
hotwire
Remember: Hotwire is about sending HTML over the wire. Keep your client-side code minimal and let Rails do what it does best - render HTML on the server.
controllers
Remember: Controllers are just the translation layer between HTTP and your application. Keep them simple and let other layers handle complexity.
performance
Remember: Premature optimization is the root of all evil. Profile first, optimize what matters, and keep solutions maintainable.