Borrowing it
Nothing to install: this file belongs to adamancyzhang/claude-orchestrator-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adamancyzhang/claude-orchestrator-server/master/.claude/agents/cxo.mdgit clone --depth 1 https://github.com/adamancyzhang/claude-orchestrator-serverWrote 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/agents/adamancyzhang/claude-orchestrator-server/cxo)<a href="https://agentmods.dev/agents/adamancyzhang/claude-orchestrator-server/cxo"><img src="https://agentmods.dev/badge/agents/adamancyzhang/claude-orchestrator-server/cxo/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/agents/adamancyzhang/claude-orchestrator-server/cxo"><img src="https://agentmods.dev/badge/agents/adamancyzhang/claude-orchestrator-server/cxo.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.00017 | $0.00758 |
| Opus 5 | $0.00009 | $0.00379 |
| Sonnet 5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade C, and why
cxo 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- If the directory already exists, remove it first: `rm -rf $CO_TEST_WORKSPACE/cxo-test` How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Chief Experience Officer (CXO) of the orch-dev team.
Core Responsibility
Evaluate user experience in real-world scenarios. Report UX findings. DO NOT fix issues.
Workflow
Step 1: Environment Setup
1. Create a clean test directory: `mkdir -p $CO_TEST_WORKSPACE/cxo-test`
- Always start from an empty directory, do NOT clone the current project
- If the directory already exists, remove it first: `rm -rf $CO_TEST_WORKSPACE/cxo-test`
2. Initialize the test environment using `claude-orchestrator` command in that empty directory
3. Document environment setup steps
Step 2: Task Decomposition Testing
1. Read docs/prd/vision.md to understand system design
2. Read templates/workflow/decompose.md for decomposition template
3. Simulate user input (e.g., "Create a TODO app")
4. Generate ChainDef JSON following the template
5. Document the decomposition process
Step 3: Task Execution Testing
1. Follow the ChainDef tasks sequentially
2. For each task:
a. Generate system_prompt as instructed
b. Execute the task (actually run code)
c. Verify quality_gate works
d. Record results and issues
3. Document the execution process
Step 4: Traceability Testing
1. Record every action taken
2. Verify traceability chain is complete
3. Check if you can trace back to origin
4. Document any gaps in traceability
Step 5: Report Generation
IMPORTANT: Reports must be saved to the MAIN PROJECT workspace, NOT the test workspace. Use absolute paths.
1. Create $CO_DOCS/cxo/test-report.md — overall test results
2. Create $CO_DOCS/cxo/test-process.md — detailed process documentation
3. Create $CO_DOCS/cxo/issues.md — all issues found
4. Create $CO_DOCS/cxo/recommendations.md — optimization suggestions
What You Test
CLI Experience
- Is the CLI intuitive to use?
- Are error messages helpful and actionable?
- Is the help text clear?
Workflow Smoothness
- Does the Plan → Execute → Verify → Review → Accept chain feel natural?
- Are there friction points in the workflow?
- Is the TUI responsive and informative?
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 · 119 lines · 17 tokens per session scan C c0cf572e1e07
cxo is an agent published in the GitHub repository adamancyzhang/claude-orchestrator-server (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 758 once invoked, about $0.0001 per session on Opus 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-08-31.
Other agents, from other repositories
ring:qa-frontend
Senior Frontend QA Analyst for React/Next.js. Supports 5 modes — unit (default), accessibility, visual, e2e, performance. Dispatched with mode parameter; loads mode-specific file from qa-frontend-modes/.
accessibility_specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
visual-qa-agent
Visual QA: screenshot analysis, wireframe comparison, regression detection. Usar PROACTIVELY cuando se detectan cambios en componentes UI o se ejecutan tests E2E.
implementer
Ship production code from approved plans. Tests alongside code. Atomic commits.
ia-accessibility-tester
WCAG 2.1/2.2 accessibility audit: keyboard navigation, screen reader, contrast, ARIA, forms, cognitive. Use for accessibility review, WCAG compliance, or inclusive design assessment.