Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/codex-security/skills/attack-path-analysis/SKILL.mdBefore choosing paths or saving retained output, read ../../references/artifact-storage.md and follow its storage policy.
Turn validated or still-plausible findings into explicit attacker stories, structured attack-path analysis facts, severity calibration, and a final reportability decision grounded in the threat model.
The path references in this skill are the default locations for this phase.
If the user explicitly provides a different path for a required input or output, use the user-provided path instead of the corresponding default path referenced in this skill.
If a required input is still missing, stop and ask the user for it before continuing.
Use the shared scan artifact path conventions in ../../references/scan-artifacts.md.
Standard scans and Deep Scan workers assess attack paths within their ordinary Standard scan workflow; neither invokes this separate phase skill.
When a workbench-backed $security-diff-scan has a scanId, load the per-scan threat model and read the validated candidates with list_codex_security_candidates({ scanId, cursor?, limit? }). Analyze every reportable or deferred candidate, preserve every discovery and validation field and the original candidate order, and submit all decisions together with one record_candidate_attack_paths({ scanId, attackPaths: [{ candidateId, attackPath }] }) call. Submit attackPaths: [] when no candidate enters this phase. The existing tool atomically updates the stored candidates; do not create per-finding reports, receipts, or manual candidate ledgers in this compact diff mode. Keep attack-path facts, counterevidence, severity calibration, and policy adjustment as separate reasoning steps. Other scan and standalone workflows retain their existing artifact behavior.
../../references/scan-artifacts.md as the repo-specific threat-model source of truth. Start from this along with the potential findings. Both inputs are required for this workflow.
reportable or survives: yes even if they were not assigned polished candidate numbers during discovery.ignore explicitly; in compact diff mode, retain its candidate record for coverage, and otherwise drop it from the surviving finding set.../../references/scan-artifacts.md. The receipt must record the candidate id, attack-path reportability decision, attack-path facts or exact proof gap, and attack-path artifact/report reference for that candidate finding.Use this checklist before finalizing the attack-path facts or policy decision:
For the most interpretive fields, explicitly ask what repository evidence suggests the opposite and why it does or does not defeat the finding:
Look specifically for repository evidence that the path is:
Apply severity and policy calibration using references/severity-policy.md.
In compact diff mode, every candidate with validation disposition reportable or deferred must receive exactly one nested attack-path decision. The recorded decisions are the complete phase output; do not also create narrative reports or receipts. Otherwise, use the following report contract.
For each surviving finding include:
Render attack-path facts using references/attack-path-facts.md.
ignore or deferred. Otherwise, every candidate that reaches attack-path analysis must leave an attack-path receipt in its candidate-ledger path from ../../references/scan-artifacts.md.../../references/scan-artifacts.md.-- Considerations for attack path --
openai/plugins
d420d13
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.