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-cleonpx skills add kryptobaseddev/cleo --skill ct-cleogit 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-cleo)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-cleo"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-cleo.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.00036 | $0.03314 |
| Opus 5 | $0.00018 | $0.01657 |
| Sonnet 5 | $0.00007 | $0.00663 |
| Haiku 4.5 | $0.00004 | $0.00331 |
Grade A, and why
ct-cleo 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLEO Protocol Guide
Full protocol content lives in ~/.cleo/templates/CLEO-INJECTION.md.
Emit any section with: cleo briefing inject --section <name>
Supported sections: session-start · work-loop · triggers · task-creation
· task-discovery · task-relationships · session-commands · memory · nexus
· orchestration · playbooks · documents · error-handling · pre-complete-gate
· spawn-tiers · rules · memory-jit · escalation
Quick Reference
| Need | Command |
|---|---|
| Start session | cleo session status → cleo briefing |
| Find work | cleo next → cleo focus <id> |
| Search tasks | cleo find "query" |
| Complete task | cleo verify T### --gate ... --evidence "..." → cleo complete T### |
| Save memory | cleo memory observe "..." --title "..." |
| Spawn subagent | cleo orchestrate spawn <taskId> --tier 2 |
| Create a Saga | cleo saga create --title "..." --acceptance "..." |
| Saga-level ready | cleo orchestrate ready <sagaId> |
| Saga-level waves | cleo orchestrate waves <sagaId> |
| Saga rollup | cleo saga rollup <sagaId> |
| List Saga members | cleo saga members <sagaId> |
| Attach doc to task | cleo docs add T### file.md --type note --slug handle |
| Read a doc | cleo docs fetch <slug> |
| Browse docs | cleo docs list --task T### |
Skill-Specific Extensions
- Task hierarchy, Saga commands, add-batch decomposition, docs policy, and CLI output details live in CLEO-INJECTION.md; emit
task-creation,documents, andpre-complete-gatewhen needed. - For add-batch input, The top-level JSON MUST be an array of task objects, not an object wrapper like
{ "tasks": [...] }. - Dry-run count semantics:
/data/countand/data/wouldCreatepredict writes;/data/insertedCountmust be0for dry-run. - Mutation output paths: use
/data/created/0,/data/updated/0, and/data/deleted/0; never parse legacy full records. - Docs path policy and strict preflight: keep docs repo-relative. Do not pass arbitrary external absolute paths. The canonical six-verb docs path is add, update, fetch, list, remove, publish (T10516). Use
cleo docs listfor discovery;cleo docs list-types(ADVANCED) andDocKindRegistryresolve runtime kinds whenlistis insufficient.
What ships with it
6 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.
- yesterday First seen · 260 lines · 36 tokens per session scan A 317f4c425e3d
ct-cleo is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 15d ago), licensed MIT. It adds 36 tokens to every session and 3,314 once invoked, about $0.0002 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…