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/jakkaj/tools/validate-v2npx skills add jakkaj/tools --skill validate-v2git clone --depth 1 https://github.com/jakkaj/toolsWrote 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/jakkaj/tools/validate-v2)<a href="https://agentmods.dev/skills/jakkaj/tools/validate-v2"><img src="https://agentmods.dev/badge/skills/jakkaj/tools/validate-v2.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.00077 | $0.03184 |
| Opus 5 | $0.00039 | $0.01592 |
| Sonnet 5 | $0.00015 | $0.00637 |
| Haiku 4.5 | $0.00008 | $0.00318 |
Grade A, and why
validate-v2 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
validate-v2
Adaptive, high-signal validation of whatever was just produced — a unified plan, tasks dossier, code change, workshop, legacy spec, or any artifact.
Prove the claims that matter, report only findings likely to change action, and spend extra review agents only when risk or uncertainty earns them.
Optimise for precision and trust first; raise recall without turning every artifact into a four-agent audit. The validator judges whether the artifact serves its reason for existing — locally correct work that does not advance its purpose still fails. It is read-only through adjudication; only mechanical, evidence-pinned document repair may follow.
User input:
$ARGUMENTS
# No flags → ADAPTIVE: lead + deterministic proof, one independent critic only for nontrivial work.
# --artifact <path> validate this file/diff (overrides conversational inference)
# --scope narrow lead + deterministic checks; at most one critic
# --scope broad lead + up to three independent critics, one per DISTINCT risk
The lead (you) owns target detection, contract derivation, commands, history ranking, routing, adjudication, repair authorization, the verdict, and persistence. Workers only propose findings — their formatting never establishes truth.
Pipeline
resolve target + revision → one compact Validation Contract → deterministic proof + cheap history
→ risk-triggered lenses → lead review + critic(s) when useful → verify & disprove every finding
→ +1 specialist only for an unresolved independent risk → compact verdict
→ safe doc repair + targeted re-check (when eligible) → compact sidecar record (when appropriate)
Load a reference only when the target needs it:
references/artifact-checks.md— per-type deterministic checks (unified plan, legacy spec, tasks, code, workshop, general).references/contract-and-forward-compatibility.md— proof levels, authority order, history labels, the five compatibility modes, next-phase traversal.references/record-template.md— sidecar placement + template.references/examples.md— worked thesis / forward-compatibility examples.
What ships with it
4 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.
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 First seen · 210 lines · 77 tokens per session scan A 73f6a7ba2181
validate-v2 is a skill published in the GitHub repository jakkaj/tools (5 stars, last pushed 18d ago), licensed MIT. It adds 77 tokens to every session and 3,184 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…