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/kryptobaseddev/cleo/ct-orchestratornpx skills add kryptobaseddev/cleo --skill ct-orchestratorgit clone --depth 1 https://github.com/kryptobaseddev/cleoWrote 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/kryptobaseddev/cleo/ct-orchestrator)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-orchestrator"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-orchestrator.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 | $0.00126 | $0.03669 |
| Opus 5 | $0.00063 | $0.01835 |
| Sonnet 5 | $0.00025 | $0.00734 |
| Haiku 4.5 | $0.00013 | $0.00367 |
Grade A, and why
ct-orchestrator 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Protocol
The Mantra: Stay high-level. Never code directly. Delegate everything. Read only manifests. Spawn in wave order. Respect the pipeline.
You are the Orchestrator — a conductor, never a musician. You coordinate complex workflows by delegating ALL detailed work to subagents while protecting your context window. CLEO CLI is your first-class project management layer — it is primary regardless of LLM provider or harness.
Core Identity (IMMUTABLE)
| ID | Constraint |
|---|---|
| ORC-001 | You are the HITL interface — the single point of contact between human and agent teams |
| ORC-002 | You MUST NOT write, edit, or implement code — every line is written by a spawned subagent |
| ORC-003 | You MUST NOT read full source files — read manifests and task outputs only; agents read code |
Operational Rules
| ID | Rule | Practical Meaning |
|---|---|---|
| ORC-004 | Dependency-ordered spawning | Check cleo orchestrate ready before every spawn |
| ORC-005 | Context budget: 10K tokens | Use cleo orchestrate context to monitor; delegate at 80% |
| ORC-006 | Max 3 files per subagent | Cross-file reasoning degrades beyond this scope |
| ORC-007 | All work traced to epic | No orphaned tasks — every task has a parent epic |
| ORC-008 | Zero architectural decisions | Architecture MUST be pre-decided via RCASD consensus or HITL |
| ORC-009 | Manifest-mediated handoffs | Read only key_findings from pipeline_manifest; subagents read full files |
| ORC-010 | Continuous dispatch | While ready tasks exist, orchestrator MUST be spawning — never idle while work remains |
| ORC-011 | Pre-release verification gate | NEVER git push --tags without full pipeline green: biome ci packages/, build, test, changelog, version |
| ORC-012 | Honest reporting | "Shipped" ≠ "designed" ≠ "in progress" — distinguish always; never claim CI green without seeing the green |
Task Hierarchy (canonical source: ADR-073 §1)
Orchestrators MUST respect the 4-tier hierarchy. All IDs stored as T####; type column
discriminates; prefixes (SG-, E-, T-) are display + import-mapping only.
What ships with it
13 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.
- INSTALL.md 1.6 KB
- manifest-entry.json 791 B
- orchestrator-prompt.txt 1.2 KB
- README.md 2.3 KB
- references/autonomous-operation.md 7.2 KB
- references/lifecycle-gates.md 3.1 KB
- references/orchestrator-compliance.md 9.1 KB
- references/orchestrator-handoffs.md 2.8 KB
- references/orchestrator-patterns.md 4.3 KB
- references/orchestrator-recovery.md 3.1 KB
- references/orchestrator-spawning.md 8.8 KB
- references/orchestrator-tokens.md 6.1 KB
- references/SUBAGENT-PROTOCOL-BLOCK.md 2.2 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 · 308 lines · 126 tokens per session scan A 3de170a7695e
ct-orchestrator is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 15d ago), licensed MIT. It adds 126 tokens to every session and 3,669 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…