Borrowing it
Nothing to install: this file belongs to pjasielski/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/pjasielski/maestro/main/CLAUDE.mdgit clone --depth 1 https://github.com/pjasielski/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/pjasielski/maestro/claude-md)<a href="https://agentmods.dev/instructions/pjasielski/maestro/claude-md"><img src="https://agentmods.dev/badge/instructions/pjasielski/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.00343 | $0.00343 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
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.
What it actually says
CLAUDE.md — Maestro Framework (Dev Repo)
Framework Instructions
See MAESTRO.md for all delivery framework behavior, commands, output standards, and conventions. MAESTRO.md is the canonical framework reference.
Artifact capture: commands save their artifact as a numbered session file; direct chat queries are answered in chat only (if an answer is extensive, ask whether to save it). /md saves a response on demand. When a file is produced, chat output = brief summary only.
Project
- Framework: Maestro (command prefix:
mae-, aliases:mex/mpoc/mrq/mds/mpl/mdo/mrv) - What this repo is: The Maestro framework itself (bootstrapping — building the framework using itself)
- Current phase: bootstrap → packaging
- Config:
maestro.toml(TOML format — Python native, no indent bugs) - Stack: Markdown-first commands, TOML config, future Python CLI (FastAPI, Pydantic AI, Typer)
- Language: Code and documentation in English
Project-Specific Notes
- This repo IS the framework — not a project using the framework
- Canonical commands in
.maestro/commands/withmae-prefix - Claude Code wrappers + aliases in
.claude/commands/ - Cursor adapters in
.cursor/rules/ - Delivery artifacts in this repo describe the framework's own design
Active Context
- Session folder:
.sessions/010-roadmap-plan-consolidation/
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 · 29 lines · 343 tokens per session scan A bbae501e1dbd
maestro CLAUDE.md is an instructions file published in the GitHub repository pjasielski/maestro (4 stars, last pushed 27d ago), licensed MIT. It adds 343 tokens to every session, about $0.0017 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.