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-docs-reviewnpx skills add kryptobaseddev/cleo --skill ct-docs-reviewgit 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-docs-review)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-docs-review"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-docs-review.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.1 | $0.00068 | $0.02698 |
| Opus 5 | $0.00034 | $0.01349 |
| Sonnet 5 | $0.00014 | $0.00540 |
| Haiku 4.5 | $0.00007 | $0.00270 |
Grade A, and why
ct-docs-review 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 2d 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.
This is a copy
88% identical to docs-review — 153 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Review Skill
@skills/_shared/cleo-style-guide.md
Through SDK (preferred)
Read the doc through the docs SSoT — not the filesystem. Reviews that grep loose files miss every doc that lives only as a blob, and miss the version history that makes "what changed?" reviews possible.
Fetch the doc to review
# By slug (preferred — stable handle survives renames):
cleo docs fetch saml-setup-draft
# By attachment ID (when the slug is unknown):
cleo docs fetch att_01HXYZ...
# By SHA-256 (when reviewing a specific version):
cleo docs fetch 7a3f9b...
cleo docs fetch returns the full attachment envelope: metadata, slug,
type, owner, refCount, and the bytes (base64-inline for files ≤ 1 MB,
storage path for larger blobs).
Diff two versions of the same doc
CLEO doesn't ship a dedicated cleo docs diff verb. Use version listing
plus two fetches to compose the diff:
cleo docs versions --for T1234 --name saml-setup-draft
# Returns every SHA-256 version with timestamps.
cleo docs fetch <sha-v1> > /tmp/v1.md
cleo docs fetch <sha-v2> > /tmp/v2.md
diff -u /tmp/v1.md /tmp/v2.md
Reviewers SHOULD anchor every issue to a specific SHA so the author can reproduce the exact state being flagged.
List candidate docs by type
cleo docs list --type spec --project # all specs in this project
cleo docs list --task T1234 --type research # research notes attached to T1234
PR review mode — still SDK-grounded
When reviewing a GitHub PR that touches a published doc, fetch the SSoT copy alongside the diff so you can compare the on-disk file in the PR against the canonical blob. Drift between the two is its own review finding — flag it as Issue N: docs SSoT drift.
gh pr diff <pr-number> -- docs/saml-setup.md
cleo docs fetch saml-setup-draft # SSoT canonical
cleo docs status # full drift report
Deprecated: Direct filesystem reads
The legacy "open the .md file in the working tree and review it"
pattern is deprecated. The on-disk file may lag the SSoT, the slug-
based linkage to the originating task is invisible, and the version
history needed for "what changed?" reviews is missing. Migrate to
cleo docs fetch <slug> for every review — and run cleo docs status
to surface drift before commenting.
What ships with it
4 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.
- 2d ago First seen · 307 lines · 68 tokens per session scan A 16c039c27aaa
ct-docs-review is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 16d ago), licensed MIT. It adds 68 tokens to every session and 2,698 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to docs-review, differing in 153 lines, and is treated as a copy.
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…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
gog-slides
Google Slides operations through gog.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…