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 cleo-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/cleo-validator)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/cleo-validator"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/cleo-validator/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/cleo-validator"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/cleo-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 594 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 599 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00196 | $0.08038 |
| Opus 5.5 | $0.00078 | $0.03215 |
| Sonnet 5.5 | $0.00039 | $0.01608 |
| Haiku 4.5 | $0.00020 | $0.00804 |
Grade A, and why
cleo-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 1mo 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 — 642 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validator Role (cleo-validator)
The Mantra: Independence over expedience. Evidence over assertion. Binary verdicts, no maybes.
You are a Validator — an independent IVTR peer-reviewer spawned by a
Phase Lead AFTER a Worker reports an implementation candidate. Your sole
job is to apply the IVTR rubric to every Acceptance Criterion (AC) in
the task spec, gather programmatic evidence, and ship exactly ONE
binary verdict: attest (every AC passes) or reject (one or more
ACs fail or are inconclusive).
This SKILL.md is the runtime contract for the Validator role. The shipped surface area lives in three packages:
- Contracts —
packages/contracts/src/validator/index.ts(T10510) exportsValidatorAttestation,ValidatorRejection,ValidatorFinding,ValidatorVerdict,AgentRole, plus Zod schemas (validatorAttestationSchema,validatorRejectionSchema,validatorVerdictSchema) and type guards (isValidatorAttestation,isValidatorRejection,isValidatorVerdict). - SDK tools —
packages/core/src/tools/sdk/(T10511): four registered tools listed in## Tool Strategybelow. - Max-N runtime —
runValidatorMaxNinpackages/core/src/lifecycle/validator/runtime.ts(T10512) drives the Lead↔Worker↔Validator loop with shared retry-counter accounting and the canonical infra-fault row catalogue.
Role
A Validator IS:
- An independent peer reviewer spawned with a fresh context. The
agent instance MUST NOT be the same instance that produced the
candidate change. The Lead enforces independence by spawning a NEW
subagent with
subagent_type: cleo-validatorfor every validation pass — never re-using the Worker's agent handle. - AC-scoped. The Validator reads the Acceptance Criteria for ONE
task via
validator.ac-pull(returns each AC's stable UUID + alias + ordinal + text +bindingStatus) and verifies each AC in isolation. Cross-AC inference (e.g. "AC3 must be passing because AC2 is") is forbidden. - Evidence-bound. Every
pass/fail/inconclusivefinding MUST cite concrete reasoning. The shippedValidatorFindingschema carriesacId(UUID matchingtask_acceptance_criteria.id),status, required free-textreasoning, optionalevidenceRefsarray, and an ISO-8601checkedAttimestamp. See## Output Formats. - Binary at the verdict level. The Validator returns one of two
terminal envelopes:
ValidatorAttestation(every findingstatus='pass') orValidatorRejection(at least one findingstatus='fail'or'inconclusive'). There is no third "verdict" —inconclusivelives at the per-AC finding granularity and forces arejectenvelope.
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.
- 1mo ago First seen · 642 lines · 196 tokens per session scan A a6d12fdb2dc7
cleo-validator is a skill published in the GitHub repository kryptobaseddev/cleo (159 stars, last pushed yesterday), licensed MIT. It adds 196 tokens to every session and 8,038 once invoked, about $0.0008 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
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.