Borrowing it
Nothing to install: this file belongs to omkhar/vulnerability-validation-skill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/omkhar/vulnerability-validation-skill/main/.agent/skills/vulnerability-validation/SKILL.mdgit clone --depth 1 https://github.com/omkhar/vulnerability-validation-skillWrote 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/omkhar/vulnerability-validation-skill/vulnerability-validation)<a href="https://agentmods.dev/skills/omkhar/vulnerability-validation-skill/vulnerability-validation"><img src="https://agentmods.dev/badge/skills/omkhar/vulnerability-validation-skill/vulnerability-validation/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/omkhar/vulnerability-validation-skill/vulnerability-validation"><img src="https://agentmods.dev/badge/skills/omkhar/vulnerability-validation-skill/vulnerability-validation.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.00149 | $0.07962 |
| Opus 5.5 | $0.00060 | $0.03185 |
| Sonnet 5.5 | $0.00030 | $0.01592 |
| Haiku 4.5 | $0.00015 | $0.00796 |
Grade A, and why
vulnerability-validation 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Validation
Use this workflow to discover new vulnerabilities (0-days) in a target repository and validate them. By default it runs native discovery: with no findings list it analyzes the code to find vulnerabilities itself; a scanner finding, researcher report, or PoC is only an optional seed. Reduce every candidate to a defensible disposition, fix true issues with minimal idiomatic patches, and leave evidence another engineer can replay.
Quick Start
For target reads, PHASE-0 starts with an external operator-controlled verifier authenticating the whole package
outside the target and neutralizing project-local discovery before startup; the loaded package cannot attest itself.
Without both proofs, stop at documentation/package compatibility with no target read. After proof and operator
authorization, record run-state.bootstrap.json, then search AI-use/security policy, threat model/boundaries,
disclosure process, and upstream sources. Collect target repository/branch, latest upstream HEAD, baseline SHA,
dirty state, finding source type, frozen snapshot or seed sources/counts, artifact root, local-only validation
environment, dependency installation/provisioning method, upstream URL, repo commands, and output mode.
Read references/portable-invariants.md and create run-state.json before triage. For the default native
discovery run, load references/discovery-intake.md; optionally run scripts/discovery_engine.py for a
first pass. Load references/artifact-contract.md when needed:
references/artifact-index.md, references/controlled-fields.md, references/closure-bundle.md,
references/drift-gate.md, references/evidence-bundle.md. Read references/review-lenses.md
before claiming review consensus and references/policy-friction.md when the LLM refuses or hedges.
What ships with it
27 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.
- references/artifact-contract.md 3.2 KB
- references/artifact-index.md 19 KB
- references/closure-bundle.md 7.6 KB
- references/controlled-fields.md 19 KB
- references/discovery-intake.md 27 KB
- references/discovery-orchestrator.md 5.5 KB
- references/discovery-playbooks.md 4.1 KB
- references/discovery-specialist-router.md 6.6 KB
- references/drift-gate.md 28 KB
- references/evidence-bundle.md 9.1 KB
- references/lane-heartbeat.md 6.5 KB
- references/loop-engineering.md 7.6 KB
- references/model-routing.md 4.5 KB
- references/policy-friction.md 8.6 KB
- references/portable-invariants.md 48 KB
- references/project-plan-gate.md 2.2 KB
- references/promoted-replay-contract.md 13 KB
- references/proof-harness-router.md 3.0 KB
- references/review-lenses.md 22 KB
- references/sanitizer-selection.md 6.4 KB
- references/shadow-skill-bootstrap.md 4.3 KB
- references/surface-tool-inventory.md 4.6 KB
- references/tool-firewall.md 10 KB
- scripts/discovery_engine.py 73 KB runs code
- scripts/quarantine_extract.py 7.1 KB runs code
- scripts/surface_tool_inventory.py 5.6 KB runs code
- scripts/validate_artifact_bundle.py 386 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.
- 1mo ago Changed fcdec5b0c18d
- 1mo ago Changed 1035f651d55c
- 1mo ago First seen · 450 lines · 149 tokens per session scan A 039d31bb8cae
vulnerability-validation is a skill published in the GitHub repository omkhar/vulnerability-validation-skill (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 149 tokens to every session and 7,962 once invoked, about $0.0006 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…