Borrowing it
Nothing to install: this file belongs to ReinaMacCredy/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/ReinaMacCredy/maestro/main/AGENTS.mdgit clone --depth 1 https://github.com/ReinaMacCredy/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/reinamaccredy/maestro/agents-md)<a href="https://agentmods.dev/instructions/reinamaccredy/maestro/agents-md"><img src="https://agentmods.dev/badge/instructions/reinamaccredy/maestro/agents-md.svg" alt="Measured on agentmods" 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.00484 | $0.00484 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
maestro AGENTS.md scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`scripts/install.sh` is the curl installer; `site/` is the Starlight docs site What it actually says
maestro
TypeScript on Bun since v0.108.0 (0.107.x was the Rust line, whose stores are
preserved under legacy/rust/). Work happens on main; the
rewrite-maestro-in-typescript branch and the .maestro/worktree/rewrite-ts
worktree are retired.
Layout: src/kernel/ is mechanism only (store, event log, sessions, cli,
loader); src/plugins/ holds verbs and policies; src/plugins/recipes/ and
src/plugins/skills/ are prompt-first markdown; bin/maestro.ts is the entry;
scripts/install.sh is the curl installer; site/ is the Starlight docs site
published by .github/workflows/pages.yml; tests/ is bun:test.
Method: maestro recipe show work for depth, ~/maestro/skills/maestro-bundle
for the tier rule (quickfix: a one-sentence diff with no Full trigger, done
directly with inline verification and no record; Light: a work item; Full: a
bundle). Bundles live in .maestro/bundle/<id>/ (SPEC/NOTES/VERIFY); NOTES.md
is an overwrite-only handoff, and history lives in the store (maestro work note, maestro trace, decisions), never in the file.
Rules:
- Toolchain: bun only (runtime,
bun:sqlite,bun:test). Install from a checkout withbun bin/maestro.ts install;maestro updatefollows that checkout, fast-forward only. - Kernel stays free of policy vocabulary (CI gate A2); no daemon, scheduler, or
detached process (A1); no escape-hatch flags such as
leanor--lane light(A3). Runbun test,bunx tsc --noEmit, and those greps before pushing. - Test-first: red test, minimal change, green; the full suite runs after install, from the checkout being installed.
- Never hand-edit the
.claude/and.codex/wiring; the installer owns those files. - Commit per verified step; never push, tag, or release unasked.
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.
- 2d ago Changed · -11 tokens per session ba869aff1d71
- 3d ago Changed · -8 lines · -228 tokens per session 3f97ff883742
- 8d ago First seen · 42 lines · 723 tokens per session scan A ac2817ad9e06
maestro AGENTS.md is an instructions file published in the GitHub repository ReinaMacCredy/maestro (231 stars, last pushed 2d ago), licensed MIT. It adds 484 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.