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

/security-scan

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

Find vulnerabilities in the current source of a whole repository or selected paths. This is the default single-pass audit. Use the diff skill for PR, commit, branch, or working-tree changes and the deep skill for an explicitly requested deep scan.

Use this Skill: https://skilld.dev/gh/openai/codex-security/security-scan

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈66 tokens for metadata: the name and description. ≈670 when used: this file. ≈4.2k more on demand in 7 files.

Description uses 3.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈263 characters, or 3.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Security Scan

Find vulnerabilities an attacker could actually exploit. Start from code that accepts untrusted input or exercises authority. Follow it to the operation it controls. Check the real enforcement point, its callers, and the strongest evidence that the suspected attack is blocked. For an exposed credential, the relevant path is who can read it and what access it grants.

Use the core audit for the independent baseline, focused investigations, and validation. Give reviewers the authorized source and security context. Keep scan administration in the parent. Report findings with source lines and concrete impact. Record what you reviewed and what remains uncertain.

Run the audit

Before reading target source, bind the requested target and scope:

  • If the SDK supplied CODEX_SECURITY_SCAN_ID and CODEX_SECURITY_SCAN_DIR, use that registered scan. Follow its launch instructions, or the SDK handoff if the SDK provided no instructions.
  • For a scan without an SDK handoff, use the managed scan tools. With a supplied scan ID, call get_codex_security_scan_context using its handoff token when supplied. Without a scan ID, a confirmed Codex desktop host calls start_codex_security_prompt_only_scan with mode: "standard". Other hosts call start_codex_security_standard_scan. Pass the requested target, scope and exact user context. If deferred, look up just the named tool. Require a running Standard scan. Keep its target, scope, phase and token, follow the account access advisory only when directed at launch, and begin the source review. Use managed scan progress at the next phase change.

Keep the target read-only and review its current source offline. Preserve exact user context as analysis data. Only the parent may read an explicitly supplied URL, once, if the user explicitly authorized that read. Do not follow links. Keep an existing investigation allowance unchanged across workers and resumes. Only if the user requests a time limit in this conversation and none was supplied, render the time budget once before source review using the requested minutes and actual UTC start and deadline.

Start the independent audit while mapping the repository. At the first usable threat model, follow save scan results. Checkpoint candidates as they arrive. Once assigned reviews return, validate each distinct broken control once and submit the findings and honest coverage to the same scan. The SDK owns finalization for its scans.

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.

No alerts8d3 checks · Risk SAFE
  • Gen Agent Trust Hub8d

    This skill facilitates automated security audits by utilizing local scripts to analyze repository source code. It includes built-in safeguards, such as explicit instructions to treat input files as data and to avoid following external links, which help maintain a secure analysis environment. The use of platform-specific commands is consistent with the skill's role as a cross-platform development tool.

  • Socket9d

    No alerts

  • Snyk8d

    Risk: LOW · No issues

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 last week

README badge

README badge for openai/codex-security/security-scan