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/IAPro-Community/Orquestrador-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/iapro-community/orquestrador-maestro/orquestrador-maestro)<a href="https://agentmods.dev/rules/iapro-community/orquestrador-maestro/orquestrador-maestro"><img src="https://agentmods.dev/badge/rules/iapro-community/orquestrador-maestro/orquestrador-maestro/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/iapro-community/orquestrador-maestro/orquestrador-maestro"><img src="https://agentmods.dev/badge/rules/iapro-community/orquestrador-maestro/orquestrador-maestro.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.00214 | $0.00214 |
| Opus 5 | $0.00107 | $0.00107 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
orquestrador-maestro 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 8d 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.
What it actually says
Orquestrador Maestro
Always use Orquestrador Maestro as the default operating contract.
Read and follow:
{{USER_HOME}}/AGENTS.md{{USER_HOME}}/.orquestrador/rules.md{{USER_HOME}}/.orquestrador/maestro.md{{USER_HOME}}/.orquestrador/SKILLS_ROUTER.json
Rules:
- The assistant acts as
orquestrador; the user is themaestro. - In projects with
DEV/, read the project DEV overview after the nearest projectAGENTS.mdand before task skills. - Keep durable project docs in
DEV/by default and updateDEV/WORKLOG.mdafter substantive work. - Consult the router before loading skills.
- Load only task-relevant skills.
- Verify before claiming completion.
- Do not commit or push unless the user explicitly asks.
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.
- 8d ago First seen · 26 lines · 214 tokens per session scan A 193631680a6f
orquestrador-maestro is a cursor rule published in the GitHub repository IAPro-Community/Orquestrador-Maestro (42 stars, last pushed today), licensed Apache-2.0. It adds 214 tokens to every session, about $0.0011 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-09-03.
Other cursor rules, from other repositories
rust-cli-conventions
Conventions for the CLI/TUI, provider abstraction, tool safety, and agent loop.
rust-native-architecture
Enforces native-first architecture and crate boundary rules for the nca workspace.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
cli-error-handling
CLI command error handling patterns.