Agent Orchestrator is a local desktop workspace for running and supervising multiple coding agents, giving each task its own session, workspace, branch, and feedback loop. It is for developers coordinating agent fleets across repositories, pull requests, CI runs, reviews, and merges. The catalogue entries are commands, skills, and instructions for working with this orchestrator.
Borrowing it
Nothing to install: this file belongs to Untrivial-ai/agent-orchestrator. 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/Untrivial-ai/agent-orchestrator/main/CLAUDE.mdgit clone --depth 1 https://github.com/Untrivial-ai/agent-orchestratorWrote 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/untrivial-ai/agent-orchestrator/claude-md)<a href="https://agentmods.dev/instructions/untrivial-ai/agent-orchestrator/claude-md"><img src="https://agentmods.dev/badge/instructions/untrivial-ai/agent-orchestrator/claude-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/untrivial-ai/agent-orchestrator/claude-md"><img src="https://agentmods.dev/badge/instructions/untrivial-ai/agent-orchestrator/claude-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.00475 | $0.00475 |
| Opus 5.5 | $0.00190 | $0.00190 |
| Sonnet 5.5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
agent-orchestrator 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 22d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- katalon-mcp-server copilot-instructions.md — 86% identical, 57 lines differ
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Read and follow AGENTS.md for repository layout, commands, coding conventions, and hard rules.
App state lives under ~/.ao 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 ~/.ao (overridable via AO_DATA_DIR/AO_RUN_FILE).
Never write AO state to ~/Library/Application Support or any other OS-default
app-data location. The sole read exception is an explicit user-initiated import
from a validated Chrome, Firefox, or Safari profile: read known source files
without modifying them and keep snapshots and results under ~/.ao.
frontend/src/main.ts pins Electron's userData to
~/.ao/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.
DESIGN.md is the current design standard and review guide. Use the approved,
repo-local reference files listed in its "Reference implementation map". Do not
infer a visual rule from another screen just because that screen exists today.
When current code conflicts with the guide, preserve functional behavior and
move the surface toward the guide in the smallest safe change. Build new UI
from shadcn primitives (components/ui/*) where a component fits, and log a
targeted migration when an existing mismatch needs broader work.
When showing or demoing frontend changes, run ao 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. ao preview updates the panel without
disrupting the current view. It does not steal focus or force the Browser tab open
if the user is looking at something else. It only badges the tab as unseen. If the
Browser tab isn't already the one
the user has open, say so in your reply (e.g. "check the Browser tab") so the change
doesn't go unnoticed behind the badge.
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.
- 22d ago Changed · +1 lines · -11 tokens per session 730b23f45906
- 1mo ago First seen · 35 lines · 486 tokens per session scan A f0f137307d48
agent-orchestrator CLAUDE.md is an instructions file published in the GitHub repository Untrivial-ai/agent-orchestrator (13,596 stars, last pushed 2d ago), licensed Apache-2.0. It adds 475 tokens to every session, about $0.0019 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-30.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.