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.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/untrivial-ai/agent-orchestrator/project)<a href="https://agentmods.dev/commands/untrivial-ai/agent-orchestrator/project"><img src="https://agentmods.dev/badge/commands/untrivial-ai/agent-orchestrator/project.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.00000 | $0.01253 |
| Opus 5 | $0.00000 | $0.00626 |
| Sonnet 5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
project 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 6d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ao project
Manage projects: register repos, inspect, configure per-project settings, and remove.
Syntax
ao project <subcommand> [args] [flags]
Subcommands
ao project add
Register a local git repo as a project so sessions can be spawned in it. The path must be an existing git repository on disk. With --as-workspace, the path may be a parent folder containing direct child git repositories; AO initializes/adopts the parent as the root repo and gitignores children.
Syntax:
ao project add [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
--as-workspace |
Register a parent folder as a workspace project (root-as-repo plus direct child repos) | - |
--id string |
Project id | Derived by the daemon from the path |
--name string |
Display name | - |
--orchestrator-agent string |
Default orchestrator session agent | - |
--path string |
Absolute path to the local git repo | Required |
--worker-agent string |
Default worker session agent | - |
Examples:
# Register a repo as a project
ao project add --path /Users/harshit/Downloads/side-quests/agent-orchestrator --name "agent-orchestrator"
# Register a workspace (parent folder containing multiple repos)
ao project add --path /Users/harshit/Downloads/side-quests --as-workspace --name "side-quests"
ao project ls
List registered projects. Aliases: ls, list.
Syntax:
ao project ls [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
--json |
Output projects as JSON | - |
Examples:
# List all registered projects
ao project ls
ao project get
Fetch one registered project.
Syntax:
ao project get <id> [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
--json |
Output project as JSON | - |
Examples:
# Get details for the agent-orchestrator project
ao project get agent-orchestrator
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.
- 6d ago First seen · 177 lines · 0 tokens per session scan A 4fb777d8c1cd
project is a command published in the GitHub repository Untrivial-ai/agent-orchestrator (10,978 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,253 tokens. 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 commands, from other repositories
sync-all
Sync skills, commands, MCP servers, and preferences between Claude, Codex, Copilot, and Cursor in one operation.
sync-from-claude
Sync skills from Claude Code (/.claude) into Codex, Cursor, or Copilot.
sync-to-cursor
Sync skills, commands, agents, hooks, rules, and MCP from Claude, Codex, or Copilot to Cursor IDE.
search-skills
Fuzzy search installed skills by name or description.
skill-diff
Compare a skill across Claude, Codex, Copilot, and Cursor to show differences.
skill-metrics
Get aggregate statistics about discovered skills including counts, quality, and token usage.