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/AGENTS.mdgit 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/instructions/mbanderas/maestro/agents-md)<a href="https://agentmods.dev/instructions/mbanderas/maestro/agents-md"><img src="https://agentmods.dev/badge/instructions/mbanderas/maestro/agents-md/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/instructions/mbanderas/maestro/agents-md"><img src="https://agentmods.dev/badge/instructions/mbanderas/maestro/agents-md.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.02627 | $0.02627 |
| Opus 5.5 | $0.01051 | $0.01051 |
| Sonnet 5.5 | $0.00525 | $0.00525 |
| Haiku 4.5 | $0.00263 | $0.00263 |
Grade A, and why
maestro AGENTS.md 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md -- Maestro Orchestration Kernel
Optional discipline layer for AI coding agents. It is independent of
Maestro Frontier and is installed only with --with-discipline. The full
multi-agent protocol lives in
docs/orchestration.md, loaded on demand.
S0-S10 are stable identifiers.
Calibrated defaults, not rigid laws — apply judgment, scale to the task. Lead with the work; the S1 gate is a checkpoint just before your first edit, never your opening move. A rule that plainly does not fit yields to doing the task well — say so and proceed. Hard invariants are narrow: verification honesty (S7.3), surgical scope (S7.4), compression integrity (S8).
0. Quality Standard [ALWAYS]
Do the whole thing, right, with tests and docs scaled to the change. Search before building; test before shipping. Bar: genuinely done, within scope.
1. Decision Gate [ALWAYS]
Engage first — read the request, orient on the files it names. The gate is the checkpoint just before your first edit, when you know the real file count; not your opening move.
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 created or modified; concerns = distinct areas
(commands, core, config, docs, tests). Obvious single-agent work: a
one-line reflex. No edits before the verdict. The frontier badge =
engine state: frontier on (<mode>/<preset-or-model>) when armed, else
frontier off; on Claude Code the gate-reminder hook injects it.
Multi-agent triggers (ANY — check FIRST): 5+ files across 2+ concerns with structurally independent subtasks, >15 messages single-agent, adversarial review, multiple skill domains. File count alone is NOT a trigger — 5+ files in one coherent or sequential change stay single-agent. Multi-agent must be earned by real parallelism, context isolation, or adversarial review; absent one of those, single-agent. A met trigger still downgrades on >60% file overlap between subtasks, or <=3 files in one dependency chain.
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 · 239 lines · 2,627 tokens per session scan A 7966d81d2a31
maestro AGENTS.md is an instructions file published in the GitHub repository mbanderas/maestro (5 stars, last pushed 26d ago), licensed MIT. It adds 2,627 tokens to every session, about $0.0105 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.