maestro-skills: Instructions file for Codex

AGENTS.md

maestro-skills AGENTS.md is an instructions file for Codex, OpenCode from ddtcorex/maestro-skills. It costs 5,720 tokens per session, scanned C, original, MIT.

Repository instructions for developing ddtcorex/maestro-skills. They require a workflow of design discussion, written planning, and test-first implementation.

In plain words
What is it for?
Guiding agents through changes in this repository, including design records, task plans, tests, implementation, and commits.
Why use it?
They give coding agents a consistent way to make changes and require TDD, which means writing a failing test before the code that makes it pass.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: reads $CODEX_HOME, but also the file is AGENTS.md. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

This is ddtcorex/maestro-skills's own configuration. It tells Codex and OpenCode how to work on maestro-skills 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-skills configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ddtcorex/maestro-skills. 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/ddtcorex/maestro-skills/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ddtcorex/maestro-skills

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ddtcorex/maestro-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/ddtcorex/maestro-skills/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5,720 This file is loaded in full into every session.
When invoked 5,720 The same file — it is already loaded in full.
Security scan C 2 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.05720 $0.05720
Opus 5.5 $0.02288 $0.02288
Sonnet 5.5 $0.01144 $0.01144
Haiku 4.5 $0.00572 $0.00572

Measured today against content hash 944bddf80c6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

maestro-skills AGENTS.md scanned grade C with 2 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 today.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

One-line installer/updater (`curl -fsSL .../install.sh | bash`). Key points if

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

One-line installer/updater (`curl -fsSL .../install.sh | bash`). Key points if
AGENTS.md · 400 lines

How it starts

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

AGENTS.md

Instructions for AI agents working in this repository. CLAUDE.md at the repo root is a symlink to this file, so Claude Code follows the same rules; Codex CLI reads AGENTS.md directly. Edit AGENTS.md only — never edit CLAUDE.md directly or replace the symlink with a copy.

Workflow: Superpowers skills are mandatory

Every change to this repository MUST follow the Superpowers skill workflow, in order:

  1. brainstorming — explore intent and design before writing anything; record the outcome in the PR description (YYYY-MM-DD-<topic>-design.md style).
  2. writing-plans — turn the approved spec into a task-by-task plan with exact test and implementation sketches; plans are transient working files, deleted once their batch ships.
  3. executing-plans — implement task by task with strict TDD: failing test first, verify RED, implement, verify GREEN, then commit that task before starting the next.

Do not skip ahead to implementation or commit while a task's tests are red.

Specs and plans: active work lives at the meta root, in maestro-harness/docs/specs/ and maestro-harness/docs/plans/, named YYYY-MM-DD-maestro-skills-<name>.md. Plans are transient and deleted once the batch ships. Once shipped, this repo commits the design record under docs/superpowers/{specs,plans}/, as the meta-root AGENTS.md states. That docs/ directory does not exist in this checkout yet; create it with the first record you commit, and never create it for in-progress work. Describe durable outcomes in the PR description as well.

Git workflow

  • Never commit to master directly; start a feature branch per work session (fix/..., feat/..., docs/...). One TDD task = one commit while executing a plan; squash at merge time if the history reads better squashed.
  • Conventional commit subjects (fix:, feat:, docs:, chore:), imperative mood.
  • Open a pull request once the branch is green; link it to the plan that produced it.

What this repo is

Read the full file on GitHub · 400 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. today Changed · +5 lines · +79 tokens per session 944bddf80c6c
  2. 14d ago Changed · -1 lines · +10 tokens per session 0647c37dc748
  3. 18d ago Changed · +14 lines · +251 tokens per session d819f9d3a2ed
  4. 24d ago Changed · +17 lines · +225 tokens per session 6c0d0ee10601
  5. 27d ago Changed 77eec61e143c
  6. 1mo ago Changed · -5 tokens per session 6fe6c83b736d
  7. 1mo ago Changed · +1 lines · +11 tokens per session 47f95418df89
  8. 1mo ago Changed · +2 lines · +33 tokens per session 8b68466e143e
  9. 1mo ago Changed · +25 lines · +401 tokens per session 3ad64f9bd49d
  10. 1mo ago First seen · 337 lines · 4,715 tokens per session scan C 79ae76d09074

Subscribe to this mod's changes

maestro-skills AGENTS.md is an instructions file published in the GitHub repository ddtcorex/maestro-skills (5 stars, last pushed yesterday), licensed MIT. It adds 5,720 tokens to every session, about $0.0229 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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

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

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