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/himkt/cafleet/clean-docsnpx skills add himkt/cafleet --skill clean-docsgit clone --depth 1 https://github.com/himkt/cafleetWrote 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/himkt/cafleet/clean-docs)<a href="https://agentmods.dev/skills/himkt/cafleet/clean-docs"><img src="https://agentmods.dev/badge/skills/himkt/cafleet/clean-docs.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.00195 | $0.04186 |
| Opus 5 | $0.00097 | $0.02093 |
| Sonnet 5 | $0.00039 | $0.00837 |
| Haiku 4.5 | $0.00019 | $0.00419 |
Grade A, and why
clean-docs 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean-Docs Skill (CAFleet-orchestrated)
One skill, three workflows — residue, affirmative, simplification —
run as the same CAFleet team shape over the same per-run process. This page is
the dispatcher and the single home of the shared orchestration spine; each
workflow body (<workflow>/<workflow>.md) carries only its own trigger
scenario, scan mechanics, artifact spec, and guarantees, citing the spine here
rather than restating it.
Required reading
Identify your coding agent first — a member's spawn prompt names it on the
CODING AGENT: line; the Director (main session) uses its own identity — then
Read your overlay and resolve it before your first action.
Load-bearing — Read in order before acting:
| # | Read | What you lose if you skip it |
|---|---|---|
| 1 | your overlay section ../../../skills/cafleet/reference/coding-agent-overlays.md#<name> — read and resolve it (see Resolve your overlay in the cafleet SKILL.md) |
you emit a literal {bg_run} / {reviewer_model} / {skill_loader} / {decision_surface}, guess a wrong value, or ignore a backend note |
| 2 | the cafleet skill's reference/base-dir.md |
the task-scope BASE resolution, the no-bypass write protocol, and the <unset> contract — you mis-root run artifacts or fall back to /tmp |
| 3 | the cafleet-design-doc skill's reference/coordination.md |
the verb + pointer + COMMENT(role) schema and this skill's extensions (scanner role, per-workflow run pointer) — your status hops mis-route |
The workflow body you route into carries its own Required-reading block for the workflow's reference pages (rubric, pattern catalog, shared review format).
Before acting, resolve every {token} you will use to its overlay value (or the
documented default); a literal {token} in any command, message, or user-facing
string is a defect.
What ships with it
14 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.
- affirmative/affirmative.md 5.1 KB
- affirmative/reference/rubric.md 2.4 KB
- affirmative/roles/reviewer.md 5.0 KB
- affirmative/roles/scanner.md 5.6 KB
- reference/review-format.md 3.8 KB
- residue/reference/patterns.md 3.7 KB
- residue/reference/rubric.md 4.4 KB
- residue/residue.md 4.8 KB
- residue/roles/reviewer.md 5.5 KB
- residue/roles/scanner.md 5.7 KB
- simplification/reference/rubric.md 1.6 KB
- simplification/roles/reviewer.md 4.5 KB
- simplification/roles/scanner.md 5.5 KB
- simplification/simplification.md 4.0 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 First seen · 290 lines · 195 tokens per session scan A 650ab7c0e4ea
clean-docs is a skill published in the GitHub repository himkt/cafleet (47 stars, last pushed 5d ago), licensed MIT. It adds 195 tokens to every session and 4,186 once invoked, about $0.0010 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-08-30.
Other skills, from other repositories
anycap-human-interaction
Collect structured visual feedback from humans using AnyCap's annotation tool, or create and iterate on diagrams using the interactive whiteboard (Excalidraw). Covers image annotation, URL/web page review with screen recording, video review, audio feedback, and collaborative diagramming with Mermaid input. Use when…
anycap-media-production
Produce media assets using AnyCap: generate images, videos, music, speech, dialogue, and complete audio scenes from text or reference inputs, refine images through interactive visual annotation, and deliver finished assets. Covers the full production workflow from concept to delivery across all media types (image…
anycap-blog-production
Turn user-provided data, notes, research, product facts, or structured inputs into AnyCap-style blog posts and then enrich those posts with first-party evidence blocks when needed. Use when a user wants a blog, article, tutorial, learn page, or SEO content draft written in the tone of the AnyCap website. Best fit when…
anycap-worldcup-predict
World Cup match prediction and pre-match intel for football (soccer) fans: predict who will win and a likely scoreline, backed by structured, verifiable evidence -- player profiles, squad dossiers, current form, head-to-head records, and past-tournament history -- using AnyCap web search and crawl. Weighs FIFA…
anycap-ai-tool-seo
Guide for planning and auditing SEO for AI tool, SaaS, and product-led websites. Powered by AnyCap -- the capability runtime that equips AI agents with web search and web crawl through a single CLI. Use when Codex needs to define SEO ICPs, map search intent to page types, inspect live SERPs, write page briefs for…
anycap-deepresearch
Guide for conducting thorough, multi-source research and producing comprehensive, well-sourced reports. Powered by AnyCap -- the capability runtime that equips AI agents with web search (including AI Grounded citations), web crawl, image generation, cloud storage, and one-click web publishing through a single CLI. Use…