Borrowing it
Nothing to install: this file belongs to mbanderas/maestro. 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/mbanderas/maestro/main/.cursorrulesgit clone --depth 1 https://github.com/mbanderas/maestroWrote 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/mbanderas/maestro/cursorrules)<a href="https://agentmods.dev/rules/mbanderas/maestro/cursorrules"><img src="https://agentmods.dev/badge/rules/mbanderas/maestro/cursorrules/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/mbanderas/maestro/cursorrules"><img src="https://agentmods.dev/badge/rules/mbanderas/maestro/cursorrules.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.02195 | $0.02195 |
| Opus 5.5 | $0.00878 | $0.00878 |
| Sonnet 5.5 | $0.00439 | $0.00439 |
| Haiku 4.5 | $0.00219 | $0.00219 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maestro -- Orchestration Kernel (Cursor)
Optional discipline layer for AI coding agents, independent of Maestro Frontier. Self-contained copy for Cursor, which does not support file imports; the full multi-agent protocol lives in docs/orchestration.md and is read on demand. Section numbers S0-S10 are stable identifiers.
Read these as calibrated defaults, not rigid laws: apply judgment and scale them to the task in front of you — every task differs. Lead with the work, not the process; the S1 orchestration decision is a quick checkpoint just before your first edit, never your opening move. A rule that plainly does not fit a task yields to doing the task well — say so and proceed. The few hard invariants are narrow: verification honesty (S7.3), surgical scope (S7.4), and compression integrity (S8).
0. Quality Standard [ALWAYS]
Do the whole thing, do it right, with tests and docs scaled to the change. Search before building; test before shipping. Bar: genuinely done. Applies within requested scope.
1. Decision Gate [ALWAYS]
Engage the task first — read the request, orient on the files it names. The gate is the checkpoint immediately before your first file edit, not your opening move: by then you know the real file count. Don't open a task with "split or not?" — that attention belongs on the work.
At that checkpoint, output one verdict line —
Maestro · frontier <on|off> — files=<n> concerns=<m> -> single-agent — <reason> or
Maestro · frontier <on|off> — files=<n> concerns=<m> -> multi-agent — <trigger met>.
files = every file the task will create or modify; concerns =
distinct areas touched (commands, core, config, docs, tests). For
obviously single-agent work the verdict is a one-line reflex — emit
it and proceed. No edits before the verdict. The frontier <on|off> badge states the
engine state — frontier on (<mode>/<preset-or-model>) when armed,
else frontier off; on Claude Code the gate-reminder hook injects
the current value.
Multi-agent triggers (ANY true — check FIRST): 5+ files across 2+ concerns, independent subtasks, >15 messages single-agent, adversarial review needed, multiple skill domains. files>=5 across 2+ concerns is multi-agent by count — independent subtasks ARE the parallel benefit. A met trigger downgrades ONLY on: >60% file overlap between subtasks, or <=3 files total in one dependency chain. Nothing else.
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 · 213 lines · 2,195 tokens per session scan A 78c2741d8e47
cursorrules is a cursor rule published in the GitHub repository mbanderas/maestro (5 stars, last pushed 26d ago), licensed MIT. It adds 2,195 tokens to every session, about $0.0088 per session on Opus 5.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-31.
Other cursor rules, from other repositories
lean-ctx-session-metrics
Shows lean-ctx (MCP) token metrics for this session at the end of each reply.
python-app
Here's how the python application is organized.
pytest-integration-tests
Below is an example test. Notice the following.
react
Cursor rule "react" from iloveitaly/llm-ide-rules, covering react, mock data, react hook form and styling.
nauro-context
Writes durable shared context into Nauro's project store so other agents (a later session or a parallel one) can discover and pull it, finds and reads context another agent left, or captures a resumable brief so your own next session in this environment picks up cleanly. Three modes. Author writes a shared brief for…
alembic-migrations
To add a non-nullable column and set a specific value for all existing rows without a persistent server default.