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 shawnclybor/clybor-claude-tooling --skill skill-validatorgit clone --depth 1 https://github.com/shawnclybor/clybor-claude-toolingWrote 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/shawnclybor/clybor-claude-tooling/skill-validator)<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/skill-validator"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/skill-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/shawnclybor/clybor-claude-tooling/skill-validator"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/skill-validator.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.00114 | $0.01764 |
| Opus 5.5 | $0.00046 | $0.00706 |
| Sonnet 5.5 | $0.00023 | $0.00353 |
| Haiku 4.5 | $0.00011 | $0.00176 |
Grade A, and why
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 4d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Validator — Ralph Loop
A continuous-iteration eval loop for skills. Geoffrey Huntley-style: run the skill, evaluate, fix, re-run until pass criteria are met or the budget is spent. The loop fails closed, not open — if the budget exhausts before pass, the skill is reported as failing with a numbered list of unmet criteria.
When to use
- After authoring a new skill, before promoting it for general use
- After editing an existing skill's prompt or pre-flight checklist
- When a skill behaves correctly in chat but fails in scripted runs (or vice versa)
- When promoting a skill from one project to another
- When validating that a skill works against a specific target repo
When NOT to use
- The skill is purely conversational with no measurable output — there's nothing to score
- The target repo is unavailable or empty — there's nothing to run against
- The skill is already covered by deterministic unit tests — those are cheaper and stricter
Inputs
SKILL_PATH— path to the skill being validated (e.g.,.claude/skills/quality-review/SKILL.md)TARGET_REPO— path to the repo the skill will run againstPASS_CRITERIA— file or inline list of required behaviors. Each criterion is a yes/no the loop can score. Format:<id>: <description>(one per line)BUDGET— max iterations (default 5) and max minutes (default 30). Hard cap; the loop fails if either is hit.
The Loop
iteration = 0
while iteration < BUDGET.max_iterations:
iteration += 1
# 1. Run skill on representative input from TARGET_REPO
output = run_skill(SKILL_PATH, sample_input(TARGET_REPO))
# 2. Score output against PASS_CRITERIA
results = score(output, PASS_CRITERIA)
if all(results.values()):
return PASS(iteration)
# 3. Identify which criteria failed and why
failures = [(id, why) for id, ok in results.items() if not ok]
# 4. Generate a targeted fix to SKILL.md
patch = propose_fix(SKILL_PATH, failures)
apply(patch)
log(iteration, failures, patch)
return FAIL(iteration, last_failures)
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.
- 4d ago Changed · +1 lines 6003e86f65b3
- 1mo ago First seen · 126 lines · 114 tokens per session scan A 06360a631b3f
skill-validator is a skill published in the GitHub repository shawnclybor/clybor-claude-tooling (6 stars, last pushed 5d ago), licensed MIT. It adds 114 tokens to every session and 1,764 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-08-31.
Other skills, from other repositories
undo
Revert recent PBR-generated commits by phase/plan, safely using git revert.
suede-ai-eval
Suede AI eval design and coverage audit: AI-SPEC, failure-mode rubric with severity scoring, concrete pass/fail eval cases, coverage and infrastructure scores, and mechanical acceptance gates. Use when a change ships LLM, RAG, agent, classifier, prompt, or generated-media behavior, or when asked to write evals for an…
suede-parity-contract
Suede AI cross-surface canon discipline: hold one canonical answer across every surface that states it (web, iOS, Android, docs, a second service) by generating a contract from the reference surface and making the others assert against it, so a divergence fails a test instead of reaching a user or an answer engine.…
verify
Verify-before-done — exercise the current change end-to-end against its acceptance criteria (the SDD plan's, or the ticket's) and report a per-criterion PASS/FAIL verdict, then record the outcome to memory. This is the concrete action that satisfies moflo's verify-before-done gate (gates.verifybeforedone / /flo -v /…
ward
Ward the codebase — an ad-hoc test-gap audit that reveals unguarded code (untested functions, uncovered edge cases, missing error-handling and integration tests) and conjures ready-to-paste test skeletons as protective wards against regression, surfaced inline in the session. Scoped to your current diff by default, or…
test-gaps
Alias for /ward — see that skill's description.