exploit-test

# Vulnetix Exploit Test Skill ## Use when - You just applied a fix and want to validate the exploit path no longer responds. - Confirming a patch deployed correctly to staging before promoting to production. - Producing a copy-pasteable test command for QA hand-off. - Comparing pre-fix vs post-fix behaviour with the same payload. - Building authorised proof-of-fix evidence for an audit. ## Don't use for - Unauthorised testing — the skill explicitly requires user-supplied authorised targets. - Live attack simulation — use a dedicated red-team tooling chain. - Generating detection rules — use `/vulnetix:detection-rules`. ## Conventions This skill follows [`_lib/contract.md`](../_lib/contract.md): the Vulnetix CLI is auto-installed by hooks, `.vulnetix/capabilities.yaml` is always present, every `vulnetix vdb` call is piped through a verified `jq` filter from [`_lib/jq/`](../_lib/jq/), independent calls run in parallel as concurrent Bash tool calls, and trailing follow-ups are limited to one line. See the contract for output style, memory write rules, and cooldowns. Builds a copy-pasteable exploit-validation command. Best used after a fix to confirm the vulnerability path no longer responds. **The user runs the command** — this skill does not auto-execute. ## Step 1: Load capabilities Read `.vulnetix/capabilities.yaml`. Specifically `binaries.nuclei`, `binaries.curl`, `binaries.docker`. ## Step 2: Fetch exploit content ```bash vulnetix vdb exploits "$ARGUMENTS" -o jso...