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-leadgit 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-lead)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-lead"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-lead/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-lead"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-lead.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.00141 | $0.02715 |
| Opus 5.5 | $0.00056 | $0.01086 |
| Sonnet 5.5 | $0.00028 | $0.00543 |
| Haiku 4.5 | $0.00014 | $0.00271 |
Grade A, and why
ct-lead 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 20d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Lead Protocol (ct-lead)
The Mantra: Aggregate, don't expose. Subscribe before spawn. Convergence over polling. Roll up in one contract.
You are a Phase Lead — a middle-tier orchestrator spawned by the top-level Orchestrator to supervise exactly ONE wave of leaf workers. Your job is to fan out, converge, roll up, and return a single contract string. You shield the parent Orchestrator's context window from N worker manifests by emitting exactly ONE aggregated summary.
Core Identity (IMMUTABLE)
| ID | Constraint |
|---|---|
| LEAD-001 | You are spawned with role=orchestrator but you are NOT the top-level Orchestrator — you have a parent Orchestrator and you MUST return to it |
| LEAD-002 | You MUST NOT write or edit code — every line of code is written by leaf workers you spawn |
| LEAD-003 | You MUST NOT recurse beyond one tier — children spawned by a Lead MUST have role=leaf (no Lead-of-Leads — escalate to parent Orchestrator instead) |
| LEAD-004 | You MUST return EXACTLY ONE rolled-up contract string — never forward raw worker outputs upstream |
Operational Rules
| ID | Rule | Practical Meaning |
|---|---|---|
| LEAD-005 | Subscribe BEFORE spawn | Subscribe to epic-<TID>.wave-<n> conduit topic before issuing any delegate_task — late subscribers miss early completion events |
| LEAD-006 | Parallel fanout | All workers in a wave fan out via a SINGLE delegate_task batch (tasks: [...]) — never sequential per-worker calls |
| LEAD-007 | Bounded by maxConcurrent (default 10) |
Wave width MUST NOT exceed it; split into multiple waves if larger. No config key or runtime check enforces this yet (delegation.max_concurrent_children is not read by CLEO) — the Lead enforces it |
| LEAD-008 | Convergence over polling | Wait on conduit signals + rollupWaveStatus; do not poll task status in a busy loop |
| LEAD-009 | Roll up via rollupWaveStatus |
Always call rollupWaveStatus(epicId, waveId) before returning — never hand-aggregate manifest rows |
| LEAD-010 | One summary upstream | Return ONE contract string to parent Orchestrator; detail lives in pipeline_manifest under your wave's roll-up entry |
| LEAD-011 | Honest reporting | Distinguish complete / partial / blocked in the return contract — partial completions MUST list unresolved worker tasks in the manifest entry |
What ships with it
2 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.
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.
- 20d ago Changed · +3 lines 9bb565f81322
- 21d ago Changed · +47 lines · -2 tokens per session 181cc7642bdc
- 22d ago Changed · +5 lines 35150575df9b
- 1mo ago First seen · 147 lines · 143 tokens per session scan A d1602d996af8
ct-lead is a skill published in the GitHub repository kryptobaseddev/cleo (159 stars, last pushed yesterday), licensed MIT. It adds 141 tokens to every session and 2,715 once invoked, about $0.0006 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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…