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 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/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/kryptobaseddev/cleo/ct-orchestrator"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00126 | $0.05391 |
| Opus 5.5 | $0.00050 | $0.02156 |
| Sonnet 5.5 | $0.00025 | $0.01078 |
| Haiku 4.5 | $0.00013 | $0.00539 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Protocol
Trustworthy project knowledge
After confirming the assigned worktree, orient with briefing/focus. Check current
coverage and sourced authority before acting on retrieved guidance. UNKNOWN
impact is incomplete assessment; NONE is no detected impact in assessed static
coverage, never proof of no runtime callers. Resolve ambiguous symbols explicitly.
Preserve historical handoffs and follow sourced corrections separately.
Consume repair findings as a matrix of scope, evidence, responsibility, operation, prerequisites, verification, and recovery. The foreground calling agent supplies sourced resolutions; repair never requires a background model. Escalate unresolved owner decisions, reject stale proposals, verify postconditions, and record useful incident learning with project/revision evidence. A failed diagnostic is not clean. Provider reference delivery must be verified or embedded self-contained; static instruction checks do not establish live Codex, Claude, or Kimi behavior.
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 |
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.1 KB
- references/lifecycle-gates.md 3.1 KB
- references/orchestrator-compliance.md 9.5 KB
- references/orchestrator-handoffs.md 2.8 KB
- references/orchestrator-patterns.md 4.3 KB
- references/orchestrator-recovery.md 2.9 KB
- references/orchestrator-spawning.md 8.8 KB
- references/orchestrator-tokens.md 6.4 KB
- references/SUBAGENT-PROTOCOL-BLOCK.md 3.3 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.
- 7d ago Changed · +23 lines a46d73ff0232
- 9d ago Changed · +2 lines 6ff0ed8d841b
- 10d ago Changed · +3 lines 36a87bb73d59
- 15d ago Changed d8718f32dadf
- 16d ago Changed · +8 lines ea153b8471d2
- 18d ago Changed · +8 lines aa8984b23daf
- 20d ago Changed · +6 lines 3b104c6ff81d
- 21d ago Changed · +14 lines 8c2fbcb33b87
- 22d ago Changed · +19 lines d24e61fd767e
- 29d ago First seen · 331 lines · 126 tokens per session scan A 84a548a25fd6
ct-orchestrator is a skill published in the GitHub repository kryptobaseddev/cleo (159 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 5,391 once invoked, about $0.0005 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.