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/commands/iapro-community/orquestrador-maestro/maestro)<a href="https://agentmods.dev/commands/iapro-community/orquestrador-maestro/maestro"><img src="https://agentmods.dev/badge/commands/iapro-community/orquestrador-maestro/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/commands/iapro-community/orquestrador-maestro/maestro"><img src="https://agentmods.dev/badge/commands/iapro-community/orquestrador-maestro/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.00000 | $0.00311 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
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 7d 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
Reidratar o Orquestrador Maestro
Se o contexto for amplo, use internamente orquestrador-maestro context brief --task "<intenção atual>" antes de abrir documentos adicionais. O Maestro continua usando apenas a conversa.
Reidrata o contexto operacional antes de continuar a tarefa atual.
Leia nesta ordem, sem abrir catálogos inteiros:
{{USER_HOME}}/AGENTS.md{{USER_HOME}}/.orquestrador/rules.md{{USER_HOME}}/.orquestrador/maestro.md- O
AGENTS.mdmais próximo do projeto atual - Se existir
DEV/, leiaDEV/README.mdouDEV/INDEX.md,DEV/HANDOFF.md,DEV/CONTEXT.mdeDEV/SPECS/ACTIVE.md - Consulte
{{USER_HOME}}/.orquestrador/SKILLS_ROUTER.jsonsomente para escolher a skill necessária
Depois de ler:
- confirme internamente que o usuário é o Maestro e você é o Orquestrador;
- retome a tarefa atual a partir do handoff e da spec ativa;
- não reinicie uma solução já concluída nem invente contexto ausente;
- se não houver handoff, diga exatamente qual contexto está faltando e peça apenas a informação mínima necessária;
- continue a execução com verificação proporcional e registre mudanças substantivas no
DEV/.
Pedido atual do Maestro:
{{input}}
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.
- 7d ago First seen · 27 lines · 0 tokens per session scan A 138d15637884
maestro is a command published in the GitHub repository IAPro-Community/Orquestrador-Maestro (41 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 311 tokens. 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 commands, from other repositories
context
Manage workflow context (handoffs, todos, session status).
factory-next
Recommend and optionally run the next factory stage for this repo.
knowledge-transfer
Interview a person to capture their operating know-how (tacit knowledge) and write it into the workspace as the company brain: processes, rules with source, glossary, decisions and open questions. For onboarding, a key person leaving, or standardizing a process.
ship
Deploy feature through automated staging validation to production with rollback testing.
ultrathink
Enter deep craftsman mode - question everything, plan like Da Vinci, craft insanely great solutions, then materialize to roadmap.
run-prompt
Delegate one or more prompts to fresh sub-task contexts with parallel or sequential execution.