maestro: Instructions file for Codex

AGENTS.md

maestro AGENTS.md is an instructions file for Codex, OpenCode from tinhtran24/maestro. It costs 2,186 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for coding agents working on Maestro, a tool with a command-line interface, background service, and desktop interface. They describe the code layout, commands, architecture, and coding conventions.

In plain words
What is it for?
Planning changes, locating relevant files, running checks, and following the project's preferred boundaries between its Go backend, Electron interface, documentation, and tests.
Why use it?
They give an agent the project context it needs before changing code, reducing the risk of editing the wrong component or following outdated behavior.

Instructions file for CodexOpenCode

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

This is tinhtran24/maestro's own configuration. It tells Codex and OpenCode 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 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.

Copy the file
curl -O https://raw.githubusercontent.com/tinhtran24/maestro/dev/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/tinhtran24/maestro

Made for: Codex, OpenCode.

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 AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tinhtran24/maestro/agents-md"><img src="https://agentmods.dev/badge/instructions/tinhtran24/maestro/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,186 This file is loaded in full into every session.
When invoked 2,186 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.02186 $0.02186
Opus 5.5 $0.00874 $0.00874
Sonnet 5.5 $0.00437 $0.00437
Haiku 4.5 $0.00219 $0.00219

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

Security

Grade A, and why

maestro AGENTS.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 1mo 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.

AGENTS.md · 163 lines

How it starts

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

AGENTS.md

Operational guidance for coding agents working in this repository. Keep changes small, match the current rewrite architecture, and prefer the documented daemon/API boundaries over behavior from the old TypeScript implementation.

Repo layout

  • backend/ — Go rewrite of Maestro: Cobra maestro CLI, loopback HTTP daemon, services, SQLite storage, lifecycle/reaper, runtime/workspace/agent/tracker adapters, terminal mux, and tests.
  • frontend/ — Electron + React supervisor wired to the daemon via the generated typed client. Treat it as a thin supervisor/UI surface; do not move daemon logic into it.
  • docs/ — current architecture/status notes. Start here before changing lifecycle, CLI, agents, storage, or daemon behavior.
  • test/ — external smoke/e2e assets, including the CLI fresh-install container check.
  • .github/workflows/ — CI definitions. Mirror these commands locally when possible.

Commands

From the repo root unless noted:

npm run lint                         # backend go test ./... + golangci-lint v2.12.2
npm run frontend:typecheck           # frontend TypeScript check
npm run sqlc                         # regenerate backend/internal/storage/sqlite/gen from queries/schema
npm run api                          # regenerate OpenAPI spec + frontend TS types (see API contract changes below)
npx @redwoodjs/agent-ci run --all    # local workflow validation; requires Docker socket

Backend-specific checks:

cd backend
go build ./...
go test ./...
go test -race ./...
go vet ./...
go run ./cmd/maestro start

Frontend-specific checks:

cd frontend
npm run typecheck
npm run build

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.

Where to look first

  • README.md — current run/config/test quickstart.
  • docs/README.md — docs index.
  • docs/architecture.md — backend mental model, package layout, lifecycle/session/service boundaries, and load-bearing rules.
  • docs/STATUS.md — what is shipped on main today and what is still in flight.
  • docs/cli/README.md — intended CLI shape: thin Cobra client over daemon HTTP, never direct storage/runtime access.
  • docs/agent/README.md — agent adapter contract and hook behavior.
  • CLAUDE.md — compatibility pointer for Claude Code; it directs agents back to AGENTS.md.

Read the full file on GitHub · 163 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. 1mo ago First seen · 163 lines · 2,186 tokens per session scan A a6a1a6170baf

Subscribe to this mod's changes

maestro AGENTS.md is an instructions file published in the GitHub repository tinhtran24/maestro (6 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 2,186 tokens to every session, about $0.0087 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-31.

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,581 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