Index of every page on this site: llms.txt
All skills
openai avatar

/attack-path-analysis

@ec0d6c1
by openaiopenai/codex-security14k stars
1,108
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/openai/codex-security/attack-path-analysis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesattack-path-facts.md

≈397 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Attack Path Facts

Use these fields to explain the path and the reportability decision. Record unknowns explicitly when they matter. Follow the calling workflow's schema; in narrative output, use concise bullets or paragraphs rather than repeating the same evidence under several headings.

  • Scope and context: the affected component, applicable threat-model boundary, whether the impact is self-only or crosses a meaningful boundary, and the evidence.
  • Attack path: attacker-controlled input, numbered attacker steps, sensitive operation, and the evidence connecting them.
  • Exposure and vector: public, internal, or admin-only access; remote, local_network, localhost, none, or unknown; relevant routing or deployment evidence when available.
  • Identity and preconditions: effective privileges, required attacker position or capabilities, plausibility of those prerequisites, and assumptions.
  • Impact: vulnerability category, affected runtime/data/identity/build/network surface, target reach, and any involved secret type or reference chain.
  • Controls and counterevidence: effective mitigations, the strongest evidence against the claimed path or scope, and why it does or does not defeat the finding.
  • Uncertainty: confidence, missing facts, and conditions that would change the assessment.
  • Decision: impact and likelihood reasoning, calibrated severity, and final policy decision.

Keep attack-path facts distinct from severity and suppression decisions. Preserve precise source locations and identifiers supplied by validation.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill provides a structured framework for analyzing security attack paths and calibrating finding severity. It includes a standard consideration for indirect prompt injection due to its processing of external security artifacts, which is handled through clear instructions for evidence-based validation.

  • Socket1d

    No alerts

  • Snyk2d

    Risk: MEDIUM · 1 issue

Signed by skilld at ec0d6c1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago

README badge

README badge for openai/codex-security/attack-path-analysis