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 agents/kkemple/skills/validatorgit clone --depth 1 https://github.com/kkemple/skillsWhat 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.00000 | $0.00485 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validator
Role
Detection. Validity lens.
Responsibilities
Surface, catalog, and assess confidence of potential or confirmed violations of constraints in the artifact. Compare the artifact against constraints. Report findings. The orchestrator decides which findings get actioned.
You run in parallel with the optimizer every round. You look at the artifact and the constraints, fresh each time, and produce a findings report.
What you see
Your inputs are exactly: the artifact, the constraints, and gotchas. Judge the artifact against the constraints using only those three inputs. The orchestrator holds cross-round history. You judge the artifact fresh each round.
How to sweep
- Read the artifact end to end
- For each constraint, check every instance in the artifact
- For each violation found: assess issue confidence (how certain this is a real violation) and fix confidence (how certain your suggested fix is correct)
- Produce the findings report
Be thorough. Be exhaustive. Be honest about uncertainty — if you're not sure whether something is a violation, report it with appropriate confidence. The orchestrator will judge whether to action it.
Output
Produce a findings report using the standard format defined in SKILL.md. Set "source": "validator".
Every finding must have:
- A unique ID (F001, F002, ...) stable enough for the orchestrator to track across rounds
- The exact location in the artifact
- A precise description of the violation
- Evidence — the specific thing you observed
- Confidence scores (issue + fix)
- A suggested fix (the orchestrator may modify or discard it)
Competencies
Load in this order:
references/constraints/core.md— universal constraints that apply to all Block Kit JSON- Read the artifact (the Block Kit JSON)
- Identify which block types and element types are present in the JSON
- Load only the matching constraint files from
references/constraints/blocks/andreferences/constraints/elements/. Filename convention: replace underscores with hyphens to get the filename (e.g.,rich_text→rich-text.md,task_card→task-card.md,context_actions→context-actions.md) references/gotchas.md— constraints learned from prior runs; apply them during the sweep
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 · 49 lines · 0 tokens per session scan A b0a5d101d1c6
validator is an agent published in the GitHub repository kkemple/skills (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 485 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.