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-skill-validatornpx skills add kryptobaseddev/cleo --skill ct-skill-validatorgit 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-skill-validator)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-skill-validator"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-skill-validator.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.00093 | $0.02384 |
| Opus 5 | $0.00046 | $0.01192 |
| Sonnet 5 | $0.00019 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
ct-skill-validator 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.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLEO Skill Validator
Full 3-phase validation loop for CLEO skills. Every phase must reach PASS before the skill is considered ecosystem-ready. Run the phases in order and iterate on failures.
Always end with the HTML report — the final deliverable to the user is the combined report opened in their browser, not terminal output.
Phase 1: Structural Compliance (Iterate to Zero Errors)
Run validate.py until the result is PASS or PASS (with warnings) with 0 errors.
Warnings are acceptable; errors are not. Fix errors and re-run.
# Full gauntlet — text output
python ${CLAUDE_SKILL_DIR}/scripts/validate.py <skill-dir>
# With manifest checks (Tier 4):
python ${CLAUDE_SKILL_DIR}/scripts/validate.py <skill-dir> \
--manifest <manifest.json> --dispatch-config <dispatch-config.json>
# JSON output (for scripting):
python ${CLAUDE_SKILL_DIR}/scripts/validate.py <skill-dir> --json
# Deep body quality audit (optional, run alongside validate.py):
python ${CLAUDE_SKILL_DIR}/scripts/audit_body.py <skill-dir>
# Manifest alignment check: bundled into validate.py Tier 4. Use:
# python validate.py <skill-dir> --manifest <manifest.json> --dispatch-config <dispatch-config.json>
# Progressive-disclosure depth check (T9684 — CI gate):
python ${CLAUDE_SKILL_DIR}/scripts/check_depth.py <skill-dir>
# Repo-wide depth sweep:
python ${CLAUDE_SKILL_DIR}/scripts/check_depth.py <repo-root> --all
# Allowlist audit (CI / cron — exit 1 on findings):
python ${CLAUDE_SKILL_DIR}/scripts/check_depth.py <skill-dir> --audit-allowlist
python ${CLAUDE_SKILL_DIR}/scripts/check_depth.py <skill-dir> --audit-allowlist --json
Depth rule (T9684): A skill PASSES when ANY of:
- SKILL.md body has ≥ 100 content lines, OR
references/subdir has ≥ 3 markdown files, ORmanifest.jsonreferences[]array enumerates ≥ 3 files (all on disk)
Pre-existing stubs are allowlisted with follow-up task IDs in
scripts/check_depth.py::ALLOWLIST. Gold-standard skills:
ct-orchestrator (9 refs) and ct-skill-creator (7 refs).
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.
- agents/ecosystem-checker.md 5.7 KB
- assets/valid-skill-example.md 341 B
- evals/quality_evals.json 2.4 KB
- evals/trigger_queries.json 970 B
- manifest-entry.json 518 B
- references/cleo-ecosystem-rules.md 6.2 KB
- references/validation-rules.md 12 KB
- scripts/_skill_finder.py 8.2 KB runs code
- scripts/audit_body.py 9.6 KB runs code
- scripts/check_depth.py 16 KB runs code
- scripts/check_ecosystem.py 5.7 KB runs code
- scripts/generate_validation_report.py 21 KB runs code
- scripts/run_quality_eval.py 4.2 KB runs code
- scripts/validate.py 21 KB runs code
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 · 237 lines · 93 tokens per session scan A 0a24dffd2095
ct-skill-validator is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 15d ago), licensed MIT. It adds 93 tokens to every session and 2,384 once invoked, about $0.0005 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…