CLI Agent Orchestrator is a tool that coordinates multiple AI coding command-line programs by running them as separate workers in isolated terminal sessions. A supervisor uses it to delegate software tasks to specialist agents in parallel or in sequence while the workers retain their normal command-line capabilities. The catalogue skills operate this orchestration workflow.
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 skills add awslabs/cli-agent-orchestrator --skill cao-contributinggit clone --depth 1 https://github.com/awslabs/cli-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/skills/awslabs/cli-agent-orchestrator/cao-contributing)<a href="https://agentmods.dev/skills/awslabs/cli-agent-orchestrator/cao-contributing"><img src="https://agentmods.dev/badge/skills/awslabs/cli-agent-orchestrator/cao-contributing/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/skills/awslabs/cli-agent-orchestrator/cao-contributing"><img src="https://agentmods.dev/badge/skills/awslabs/cli-agent-orchestrator/cao-contributing.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.00153 | $0.04357 |
| Opus 5.5 | $0.00061 | $0.01743 |
| Sonnet 5.5 | $0.00031 | $0.00871 |
| Haiku 4.5 | $0.00015 | $0.00436 |
Grade C, and why
cao-contributing scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
( trap 'rm -rf "$TMPH"' EXIT # cleans up on every path How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing to CAO
How to make a change to the cli-agent-orchestrator codebase and get it through CI
cleanly. Read this before pushing a branch or opening a PR. The canonical human docs are
DEVELOPMENT.md, CONTRIBUTING.md, and
CODEBASE.md — this skill is the operational checklist that mirrors what
CI actually enforces.
Golden rules (read these first)
- Run Python tooling through
uv.uv sync --all-extras --dev,uv run pytest …,uv run mypy src/,uv run cao …. There is no barepipworkflow, and the venv CI builds is the oneuvmanages. Repo scripts are documented in their own text as plainpython scripts/<name>.py(for examplescripts/sync_skills.py, whose fix-up message andtest_skill_packaging_parity.pyboth quote that form) — run them asuv run python scripts/<name>.py, which satisfies both. - Verify the actual CI run after every push — never declare "done" on local tests
alone. Poll it:
gh pr checks <number>for every workflow on the PR, orgh run list --branch <branch> --workflow CIforci.ymlalone, thengh run view <id>/gh run view <id> --log-failed. - When a required check fails unexpectedly, diff EVERYTHING your commit changed —
including CI/workflow/config files (
.github/workflows/*.yml,pyproject.toml,mypy.ini) — before concluding the cause is pre-existing or external. The signal is often in your own diff (git diff <base>..HEAD -- .github/). A displaced one-line workflow key (see the mypy note below) can turn a tolerated warning into a hard failure. - Never mark a task complete while a required CI gate is red. A red gate means not done; investigate, don't rationalize.
- Match the repo, don't reshape it. Don't bundle unrelated fixes (e.g. repo-wide type errors) into a feature PR, and don't tighten a CI policy as a side effect of an unrelated change.
Local dev loop
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.
- 3d ago Changed · +1 lines 89fcdc3f466f
- 4d ago Changed ec76f89d029c
- 9d ago Changed · +1 lines e47110c53838
- 10d ago Changed · +7 lines d0d5393c1a32
- 13d ago Changed · +8 lines ece2b40d5764
- 14d ago Changed · +1 lines d5a1e979cc92
- 21d ago First seen · 203 lines · 153 tokens per session scan C 977904825dbb
cao-contributing is a skill published in the GitHub repository awslabs/cli-agent-orchestrator (1,438 stars, last pushed yesterday), licensed Apache-2.0. It adds 153 tokens to every session and 4,357 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-26.
Other skills, from other repositories
beevibe-verify-pr
CI verification before marking a PR-bearing task done. Use BEFORE calling mcpbeevibeupdateprogress(done) on any session whose deliverable is a pull request — including the first dispatch (you opened the PR with gh pr create) and any revision dispatch (you pushed new commits to an existing PR). Watches the PR's…
appveyor-automation
Automate Appveyor tasks via Rube MCP (Composio). Always search tools first for current schemas.
e2e-testing-expert
Expert guide for End-to-End (E2E) testing with Playwright, unit/integration testing with Vitest, and CI/CD automated testing pipeline setup / Panduan ahli pengujian End-to-End (E2E) dengan Playwright, pengujian unit/integrasi dengan Vitest, dan otomatisasi CI/CD.
skill-engineering-quality
Use when a repository needs a quality baseline or modernization across one or more detected application stacks, especially linting, formatting, type checking, tests, build validation, developer tooling, hooks, or CI consistency.
Verify before done
Use before claiming work is complete — prove it with commands, do not assume.
Test-first
Use before implementing a feature or bugfix — write the failing test before the code.