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.
git 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/mcp/awslabs/cli-agent-orchestrator/cao-cao-ops)<a href="https://agentmods.dev/mcp/awslabs/cli-agent-orchestrator/cao-cao-ops"><img src="https://agentmods.dev/badge/mcp/awslabs/cli-agent-orchestrator/cao-cao-ops/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/mcp/awslabs/cli-agent-orchestrator/cao-cao-ops"><img src="https://agentmods.dev/badge/mcp/awslabs/cli-agent-orchestrator/cao-cao-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
cao-ops 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 7d 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
{
"cao-ops": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"cli-agent-orchestrator==2.5.3",
"cao-ops-mcp-server"
]
}
}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.
- 7d ago Changed 605d3f1baa1d
- 25d ago First seen · 11 lines scan A 11ff374cb503
cao-ops is an MCP server published in the GitHub repository awslabs/cli-agent-orchestrator (1,430 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-09-21.
Other mcp servers, from other repositories
agentbraid
MCP server "agentbraid" as configured in xuu33030/agentbraid. Runs locally from the agentbraid Python package.
work-buddy
MCP server "work-buddy", hosted remotely at localhost, as configured in KadenMc/work-buddy.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm --prefix test/mcp run start-stdio.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.