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
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git 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/commands/untrivial-ai/agent-orchestrator/status)<a href="https://agentmods.dev/commands/untrivial-ai/agent-orchestrator/status"><img src="https://agentmods.dev/badge/commands/untrivial-ai/agent-orchestrator/status.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.00111 |
| Opus 5 | $0.00000 | $0.00056 |
| Sonnet 5 | $0.00000 | $0.00022 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
status 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 8d 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.
What it actually says
ao status
Show AO daemon status. Use this to verify the daemon is up and check which port it is bound to.
Syntax
ao status [flags]
Flags
| Flag | Meaning | Default / Required |
|---|---|---|
--json |
Output status as JSON | - |
Examples
# Check daemon status
ao status
# Get status as JSON (e.g. to check port programmatically)
ao status --json
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.
- 8d ago First seen · 28 lines · 0 tokens per session scan A c6053da9fe06
status is a command published in the GitHub repository Untrivial-ai/agent-orchestrator (11,075 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 111 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-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-trace-enable
Enable skill tracing to track which skills are loaded and invoked.
sync-from-claude
Sync skills from Claude Code (/.claude) into Codex, Cursor, or Copilot.
sync-to-copilot
Sync skills and instructions from Claude or Codex to GitHub Copilot CLI.