Borrowing it
Nothing to install: this file belongs to aaryansinha16/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/aaryansinha16/Maestro/main/CLAUDE.mdgit clone --depth 1 https://github.com/aaryansinha16/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/aaryansinha16/maestro/claude-md)<a href="https://agentmods.dev/instructions/aaryansinha16/maestro/claude-md"><img src="https://agentmods.dev/badge/instructions/aaryansinha16/maestro/claude-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.03702 | $0.03702 |
| Opus 5 | $0.01851 | $0.01851 |
| Sonnet 5 | $0.00740 | $0.00740 |
| Haiku 4.5 | $0.00370 | $0.00370 |
Grade A, and why
Maestro CLAUDE.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 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.
How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maestro — CLAUDE.md
Project Identity
Maestro is an autonomous project management system for solo developers managing multiple GitHub projects in parallel. It runs on a server, schedules background work sessions across projects, makes meaningful progress autonomously, and reports back through a web dashboard and daily briefings.
The core problem it solves: a solo developer with 4-5 active projects cannot give equal attention to all of them. Some projects stagnate while others get attention. Maestro acts as a parallel workforce — autonomous agents that work on each project on a schedule, advancing real tasks while the developer focuses on whichever project is most important right now.
This is NOT a CI/CD tool. This is NOT a noise commit generator. This is a serious AI engineering system that produces code worth merging.
Core Operating Principles
These are non-negotiable. Every architectural decision must respect these.
-
Quality over activity. If there's nothing meaningful to do on a project, the agent does nothing and reports back. Empty days are acceptable. Noise commits are not.
-
Time-bounded autonomy. Each session is bounded (default 45 minutes). The agent makes its own decisions within that window, then stops, commits, and reports.
-
PR-first workflow. The agent never pushes directly to main. It creates feature branches and opens PRs. The developer reviews and merges.
-
Quality gates before PR. Before opening a PR, the agent must verify: tests pass, lint passes, types compile. If quality gates fail, it commits the work to a branch flagged "needs review" but doesn't open a PR.
-
The state file is the truth. Every project has a
.maestro/directory. State, journal, and decisions live there. The git repo is the canonical store. No machine-specific state. -
Daily review is mandatory. The developer reviews briefings within 24 hours. The system is designed assuming this happens.
-
The developer is the contributor. All commits use the developer's git identity. The agent is a tool. The developer reviews, approves, and ships.
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 · 346 lines · 3,702 tokens per session scan A 4a0d03170316
Maestro CLAUDE.md is an instructions file published in the GitHub repository aaryansinha16/Maestro (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3,702 tokens to every session, about $0.0185 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-08-31.
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.