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.
npx agentmods add skills/untrivial-ai/agent-orchestrator/using-aonpx skills add Untrivial-ai/agent-orchestrator --skill using-aogit clone --depth 1 https://github.com/Untrivial-ai/agent-orchestratorWhat 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 | $0.00062 | $0.00829 |
| Opus 5 | $0.00031 | $0.00415 |
| Sonnet 5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
using-ao 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 yesterday.
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AO CLI Catalog
ao is a thin CLI over the local AO daemon. Every command is ao <command> --help for the authoritative flag list.
| Command | What it does | When to use | Details |
|---|---|---|---|
spawn |
Spawn a worker agent in a fresh git worktree | Starting a new task or issue | commands/spawn.md |
session |
Manage agent sessions (list, kill, rename, restore, etc.) | Inspecting or controlling running/terminated sessions | commands/session.md |
project |
Register, inspect, configure, or remove projects | Setting up or managing repos AO knows about | commands/project.md |
orchestrator |
List orchestrator sessions | Viewing which sessions are orchestrators | commands/orchestrator.md |
review |
Submit a reviewer result for a worker's PR | Completing a code review loop | commands/review.md |
send |
Send a message to a running agent session | Correcting or directing a live agent | commands/send.md |
preview |
Start a session-owned app or open an exact URL/file | Running and showing the worker's relevant app, Markdown, HTML, PDF, or image | commands/preview.md |
browser |
Inspect and control the session's shared live browser | Verifying a web app through snapshots, interactions, waits, screenshots, console, and errors | commands/browser.md |
start |
Fetch (if needed) and open the AO desktop app | Launching the app | commands/start.md |
stop |
Stop the AO daemon | Shutting down AO | commands/stop.md |
status |
Show daemon status | Verifying the daemon is up and healthy | commands/status.md |
doctor |
Run local health checks | Diagnosing AO setup problems | commands/doctor.md |
import |
Import projects from a legacy AO install | Migrating from the old flat-file store | commands/import.md |
version |
Print version information | Checking installed version | - |
completion |
Generate shell completion scripts | Setting up tab completion | - |
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- commands/browser.md 8.6 KB
- commands/doctor.md 400 B
- commands/import.md 1017 B
- commands/orchestrator.md 506 B
- commands/preview.md 5.2 KB
- commands/project.md 4.8 KB
- commands/review.md 1.2 KB
- commands/send.md 665 B
- commands/session.md 3.6 KB
- commands/spawn.md 1.6 KB
- commands/start.md 531 B
- commands/status.md 400 B
- commands/stop.md 366 B
- references.md 2.8 KB
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.
- yesterday First seen · 45 lines · 62 tokens per session scan A 3aa01b1ecb5f
using-ao is a skill published in the GitHub repository Untrivial-ai/agent-orchestrator (10,763 stars, last pushed today), licensed Apache-2.0. It adds 62 tokens to every session and 829 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
test-workflow
Automated testing workflow that combines Playwright testing, Slack GIF recording, and test report generation. Use when user mentions "测试"、"test"、"Playwright" or asks for QA/testing workflows. Automatically generates: (1) Test execution with Playwright, (2) Slack-optimized GIF of test process, (3) Screenshot at each…
high-fidelity-extraction
Advanced protocol for extracting granular social media and web intelligence using browser automation and DOM analysis.
threejs-fundamentals
Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
analyze-performance-traces
Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and…