Borrowing it
Nothing to install: this file belongs to tinhtran24/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/tinhtran24/maestro/dev/CLAUDE.mdgit clone --depth 1 https://github.com/tinhtran24/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/tinhtran24/maestro/claude-md)<a href="https://agentmods.dev/instructions/tinhtran24/maestro/claude-md"><img src="https://agentmods.dev/badge/instructions/tinhtran24/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.00405 | $0.00405 |
| Opus 5 | $0.00202 | $0.00202 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
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 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
CLAUDE.md
Read and follow AGENTS.md for repository layout, commands, coding conventions, and hard rules.
App state lives under ~/.maestro only
All app state, the daemon's data dir, running.json, worktrees, and the Electron
supervisor's userData (Chromium cache, cookies, local/session storage, crash
dumps), must resolve under ~/.maestro (overridable via MAESTRO_DATA_DIR/MAESTRO_RUN_FILE).
Never write to or read from ~/Library/Application Support or any other OS-default
app-data location. frontend/src/main.ts pins Electron's userData to
~/.maestro/electron; do not remove that override. See the hard rule in AGENTS.md.
Design System
Always read DESIGN.md before making any visual or UI decision —
start with the "clone maestro verbatim" banner at the top, which
governs the current look.
The renderer clones the maestro web app verbatim
(~/Projects/maestro/packages/web/src) in looks and design, with a
refined-blue accent and the terminal keeping its own palette. This supersedes the
older "match emdash" framing in DESIGN.md (per explicit user decision 2026-06-10).
Build new UI from shadcn primitives (components/ui/*) where a component fits. Do not
deviate without explicit user approval. In QA/review, flag any renderer code that
diverges from maestro — do not re-flag emdash mismatches.
When showing or demoing frontend changes, run maestro preview [url] from inside the
session so the change renders in the desktop browser panel (the inspector rail's
Browser tab); do not just describe it.
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 · 31 lines · 405 tokens per session scan A b30463c7bf36
maestro CLAUDE.md is an instructions file published in the GitHub repository tinhtran24/maestro (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 405 tokens to every session, about $0.0020 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
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).
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.
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 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).
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.