Borrowing it
Nothing to install: this file belongs to Traves-Theberge/Orchestra. 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/Traves-Theberge/Orchestra/main/AGENTS.mdgit clone --depth 1 https://github.com/Traves-Theberge/OrchestraWrote 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/traves-theberge/orchestra/agents-md)<a href="https://agentmods.dev/instructions/traves-theberge/orchestra/agents-md"><img src="https://agentmods.dev/badge/instructions/traves-theberge/orchestra/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.
<a href="https://agentmods.dev/instructions/traves-theberge/orchestra/agents-md"><img src="https://agentmods.dev/badge/instructions/traves-theberge/orchestra/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00772 | $0.00772 |
| Opus 5.5 | $0.00309 | $0.00309 |
| Sonnet 5.5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
Orchestra 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 20d 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.
How it starts
The opening of the file, as written. The whole thing — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Required ADE Reference Patterns
For ADE changes, inspect the relevant Orca and T3 Code patterns before implementation. Follow the pinned source registry and package mapping in docs/superpowers/plans/ade-2026-10-03/reference-patterns.md. Record the source revision, observed behavior, Orchestra adaptation, deliberate deviations, and behavioral verification in the package handoff. Both references must be considered; if one has no relevant pattern, document that finding. Preserve the Kanban model while integrating native provider chat and a shared orchestration control/observation layer. Reference code, documentation, and passing unit tests do not establish Orchestra's E2E reliability; verify each claimed capability independently.
Project Structure & Module Organization
The repository's Orchestra CLI skill is .codex/skills/orchestra-cli/SKILL.md. Keep its command examples and references/task-system.md aligned with executable CLI help, shared task semantics, and behavioral verification whenever CLI/task behavior changes. Planned commands must stay explicitly marked as unavailable.
apps/backend contains the Go API server and orchestration logic. Put binaries in cmd/ and application code in internal/. apps/tui is a separate Go module for the terminal dashboard. apps/desktop is the Electron + React client; renderer code lives in src/, Electron entrypoints in electron/, static assets in public/, and dev scripts in scripts/. Shared schemas live in packages/protocol/schemas, test fixtures in packages/test-fixtures, and longer-form references in docs/ and ops/.
Build, Test, and Development Commands
cd apps/backend && go test ./... && go build -o orchestrad ./cmd/orchestrad/: run backend tests and build the server.cd apps/tui && go test ./...ormake dash: test or launch the TUI.cd apps/desktop && npm install && npm run dev: start the desktop app with Vite + Electron.cd apps/desktop && npm run typecheck && npm run test && npm run build: validate TypeScript, run Vitest, and build production assets.cd apps/desktop && npm run smoke:ops:go: run the desktop smoke flow against a spawned backend.
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.
- 20d ago Changed · +5 lines · +198 tokens per session 4a28d2c4d329
- 22d ago First seen · 21 lines · 574 tokens per session scan A 2b0dd9f28a1e
Orchestra AGENTS.md is an instructions file published in the GitHub repository Traves-Theberge/Orchestra (26 stars, last pushed 10d ago), licensed Apache-2.0. It adds 772 tokens to every session, about $0.0031 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-10-02.
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).
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.
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).
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 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).
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.