maestro: Instructions file for Claude Code

CLAUDE.md

maestro CLAUDE.md is an instructions file for Claude Code from SnapdragonPartners/maestro. It costs 5,317 tokens per session, scanned A, original, MIT.

Repository instructions for Claude Code, the command-line coding assistant, in the Maestro Go project. They explain which documents and code to trust, how the project’s version 2 work is organized, and how changes should be developed and reviewed.

In plain words
What is it for?
Use them when planning or implementing Maestro changes, checking project authority, following its state-machine workflow, managing branches and reviews, or recording spikes and deferred work.
Why use it?
They give the agent a shared source of truth for project decisions and workflows. They also prevent edits to the frozen version 1 code and keep linked instruction files consistent.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

This is SnapdragonPartners/maestro's own configuration. It tells Claude Code how to work on maestro itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything maestro configures →

Reuse

Borrowing it

Nothing to install: this file belongs to SnapdragonPartners/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.

Copy the file
curl -O https://raw.githubusercontent.com/SnapdragonPartners/maestro/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/SnapdragonPartners/maestro

Made for: Claude Code.

Wrote 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.

agentmods badge for maestro CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/snapdragonpartners/maestro/claude-md/github.svg)](https://agentmods.dev/instructions/snapdragonpartners/maestro/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/snapdragonpartners/maestro/claude-md"><img src="https://agentmods.dev/badge/instructions/snapdragonpartners/maestro/claude-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.

agentmods 80×15 button for maestro CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/snapdragonpartners/maestro/claude-md"><img src="https://agentmods.dev/badge/instructions/snapdragonpartners/maestro/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5,317 This file is loaded in full into every session.
When invoked 5,317 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.05317 $0.05317
Opus 5.5 $0.02127 $0.02127
Sonnet 5.5 $0.01063 $0.01063
Haiku 4.5 $0.00532 $0.00532

Measured 29d ago against content hash ead9ca8e06e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 29d 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.

CLAUDE.md · 447 lines

How it starts

The opening of the file, as written. The whole thing — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Operating instructions for Claude Code in this repository. AGENTS.md is a tracked symbolic link to this file (Git mode 120000; verify with git ls-files -s AGENTS.md), so edit CLAUDE.md only and both entry points stay in sync. Tooling that enumerates only regular files may not list AGENTS.md; that does not mean it is absent.

Project And Authority

Maestro is a Go application for coordinating AI agents to turn product intent into reviewed repository changes. Active development is the breaking v2 redesign. v1 remains the current implementation until replaced, but is frozen: do not fix v1 defects unless they block v2 work.

Use the source appropriate to the question.

For current runtime behavior, precedence is:

  1. Code and tests.
  2. Canonical FSM docs: pkg/pm/STATES.md, pkg/architect/STATES.md, and pkg/coder/STATES.md.
  3. README.md, and the routing table below for where to look.
  4. deprecated v1 docs, as unverified orientation only.

For v2 design intent, precedence is:

  1. Accepted ADRs (status = "live") in docs/adr/.
  2. Live phase artifacts in docs/v2/phase_x/.
  3. The roadmap and other cross-phase documents in docs/v2/.
  4. Historical ADRs 0001–0016, as non-binding context only.

Documents with status = "archive" carry no authority. When code and a v2 ADR differ, the code describes today and the ADR describes the accepted direction. Start with docs/README.md, docs/adr/README.md, and the applicable phase README.md; do not treat a referenced deprecated document as authoritative.

Binding V2 Workflow

docs/v2/process_build.md is the binding working agreement for building v2. It binds Claude, Codex, and DR and wins over this file if they disagree. The current phase scope and plan at docs/v2/phase_x/plan_scope.md binds work in that phase. docs/v2/plan_roadmap.md defines the phase sequence and cross-phase decisions.

Throughout this file and the v2 docs, phase_x is a placeholder for the current phase number — the real directories are docs/v2/phase_0/, phase_1/, phase_2/, and so on. The same convention appears in ADR 0017 and process_build.md, so it is written this way here to match rather than diverge.

Read the full file on GitHub · 447 lines

Changes

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.

  1. 29d ago Changed · +10 lines · +175 tokens per session ead9ca8e06e3
  2. 1mo ago Changed · +1 tokens per session ccd9a4b6af9d
  3. 1mo ago Changed · +97 lines · +1,281 tokens per session 4f39390d6745
  4. 2mo ago First seen · 340 lines · 3,860 tokens per session scan A 0f0ceaf2d460

Subscribe to this mod's changes

maestro CLAUDE.md is an instructions file published in the GitHub repository SnapdragonPartners/maestro (25 stars, last pushed 23d ago), licensed MIT. It adds 5,317 tokens to every session, about $0.0213 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-30.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens