Terminal
Terminal/Skill
Checks whether a security fix really closes a reported vulnerability, returning fixed, still vulnerable, or inconclusive per finding.
By OpenAI
Works with
npx skills add openai/codex-security --skill verify-fixInvoke this skill only for an explicit request to verify a security fix, including a direct $verify-fix invocation. A request to implement a fix or run its tests does not by itself request this skill. For other tasks, follow the user's requested workflow and response format without applying this skill's JSON result contract.
Determine whether each supplied security finding has been fixed in the current checkout. Operate in standalone verification-only mode; do not create, modify, or delete repository files, apply patches, commit changes, write artifacts, or modify issue trackers.
Use ../../references/static-finding-assessment.md to identify the original attacker-controlled source, security control, sensitive sink, reachable path, trust boundary, counterevidence, and proof gaps. If the caller already supplied that reference in the prompt, use the supplied contents without reading it again.
Return exactly one JSON object:
{
"results": [
{
"id": "finding-or-issue-id",
"status": "fixed|still_vulnerable|inconclusive",
"evidence": "specific current source, exploit, test, or proof-gap evidence"
}
]
}
fixed only when evidence proves the original security boundary is closed and legitimate behavior remains intact.still_vulnerable only when evidence proves the original vulnerable path remains reachable.inconclusive for a repository mismatch, missing original context, unavailable relevant checks, an unproven legitimate control, or another material proof gap.Never infer a stronger verdict by weakening the read-only boundary, substituting a different vulnerability, or hiding missing evidence.