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-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/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-cleo"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-cleo.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.00036 | $0.07247 |
| Opus 5.5 | $0.00014 | $0.02899 |
| Sonnet 5.5 | $0.00007 | $0.01449 |
| Haiku 4.5 | $0.00004 | $0.00725 |
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 3d 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 — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLEO Protocol Guide
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 calling agent supplies sourced resolutions; no background model is required. 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.
Asking the owner (HITL ask tool)
Whenever you need the owner to answer, decide, approve or choose ANYTHING, use the ask
tool (AskUserQuestion in Claude Code, or the provider equivalent listed in CAAMP's
PROVIDER_ASK_TOOLS) with 2-4 concrete, selectable options, recommended first, each stating
what happens and its trade-offs. Never ask inside a response or bury a question in prose.
Answer first in every reply: the first line is the result, answer or decision; then only the
evidence the reader needs and what was skipped or unverified. No preamble, recap or routine
status chatter: report only when done or when a decision is needed.
- Subagents never ask the human. Return the question with its options to your
orchestrator (
blockedplus{question, options[{label, description}], recommended}in the manifest); the orchestrator asks via its ask tool. - No ask tool in the harness: emit one LAFS
hitl.requestenvelope{question, options[{label, description}], recommended}and stop.
What ships with it
8 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.
- __tests__/ct-cleo-skill.test.ts 8.6 KB runs code
- __tests__/injection-content.test.ts 9.1 KB runs code
- references/anti-patterns.md 971 B
- references/loom-lifecycle.md 5.1 KB
- references/memory.md 2.3 KB
- references/orchestrator-constraints.md 1.3 KB
- references/session-protocol.md 4.8 KB
- references/sticky-notes.md 1.1 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.
- 3d ago Changed fd0f0b404ae6
- 6d ago Changed 1d5d896615b5
- 7d ago Changed 5ed49b5aaf42
- 9d ago Changed 01013b11465d
- 10d ago Changed · -1 lines d05c9a6da1f7
- 16d ago Changed 81d369efbb61
- 18d ago Changed ceccd388207d
- 20d ago Changed 0ea7a2947f60
- 21d ago Changed · +17 lines 4eb0413fd110
- 22d ago First seen · 451 lines · 36 tokens per session scan A 6dd72f4263bc
ct-cleo is a skill published in the GitHub repository kryptobaseddev/cleo (159 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 7,247 once invoked, about $0.0001 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.