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-leangit 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-lean)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-lean"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-lean/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-lean"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-lean.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00126 | $0.01588 |
| Opus 5.5 | $0.00050 | $0.00635 |
| Sonnet 5.5 | $0.00025 | $0.00318 |
| Haiku 4.5 | $0.00013 | $0.00159 |
Grade A, and why
ct-lean 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 today.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ct-lean — the smallest complete change
The best code is the code never written. Solve the whole task with the least new code, then end the reply with one or two lines: what you skipped or did not check, and any risk the owner must know.
Levels
| Level | What changes |
|---|---|
lite |
Build what was asked. When a smaller option fully works, name it in one line and let the owner pick. |
full |
The rules below. Default. |
ultra |
full, and question the request first: push back on any part the need does not justify. |
off |
No lean rules. |
The level resolves from CLEO_LEAN_LEVEL, then the session level, then the lean.level
config key, then full. When the owner asks for a level ("go ultra", "lean off"), set it:
cleo lean level ultra --session for this session, cleo lean level lite for the project,
--global for every project. cleo lean level alone shows the level and its source.
cleo lean gain --card shows the measured benchmark scoreboard: averages, never a number
for this repo.
Before you write
Read the task (cleo show <id> --full) and the code it touches. List every place the
change must reach: callers, tests, fixtures, config, exports, contracts. Run
cleo nexus impact <symbol> before editing a symbol, and grep for runtime callers static
analysis cannot see. Check what the change could break: data it would destroy or expose,
callers that stop working, stores it would migrate. That is scope. Extra features are not.
Take the first option that fully works
- Does it need to exist? Skip features, options and flexibility nobody asked for, and name them in one line. A vague request gets the smallest version that does the core job.
- Already in this codebase? A helper, accessor, contract or pattern: use it the way the
surrounding code does. Search
packages/core/srcandpackages/contracts/srcfirst. - Standard library or platform feature? Use it, unless the repo has its own (a house
chokepoint such as
openDualScopeDborcleo runbeats a raw primitive). - An installed dependency? Use it. Never add a dependency for a few lines.
- One line a reader gets at a glance? One line.
- Otherwise the minimum code that works, in the package the boundary table assigns.
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.
- today Changed · +7 lines · +32 tokens per session 83f62c89ea72
- 2d ago Changed · +3 lines 90a9b91f62db
- 3d ago Changed · +18 lines c8cc0b4317df
- 6d ago First seen · 92 lines · 94 tokens per session scan A 1b727b53440c
ct-lean is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 1,588 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-10-11.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…