security-scan
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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 1.4w
- Forks
- 1.1k
01 前言 Front Matter
- name
- security-scan
- description
- 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.
02 资源文件 7
- 参考文档agents/openai.yaml245 B
- 参考文档references/desktop-scan.md580 B
- 参考文档references/managed-scan.md1.3 KB
- 参考文档references/scan-artifacts-and-ledger.md6.9 KB
- 参考文档references/scan-results.md2.8 KB
- 参考文档references/scoped-paths.md2.3 KB
- 参考文档references/sdk-files.md2.1 KB
03 SKILL.md 正文
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_IDandCODEX_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_contextusing its handoff token when supplied. Without a scan ID, a confirmed Codex desktop host callsstart_codex_security_prompt_only_scanwithmode: "standard". Other hosts callstart_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.
04 同仓库更多 Skills
vulnerability-writeup
Turn vulnerability notes, disclosure reports, PoCs, source code, or Codex Security findings into self-contained vulnerability reports with clearly supported claims. Use for one vulnerability or a disclosure campaign; a Codex Security scan is optional.
verify-fix
Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability. Do not invoke automatically while implementing fixes, reviewing ordinary code changes, or running tests. Do not use for non-security fixes, candidate finding validation, or full repository scans.
validation
Use when Codex is already in the validation phase of a security scan or the user explicitly asks to determine whether one or more candidate security findings are valid. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
triage-finding
Triage supplied or imported security findings against a repository using its security policy and static code evidence. Accepts scanner reports, advisories, GitHub findings, and Jira or Linear tickets. Do not use for discovery, duplicate triage, runtime validation, or fixes.
track-findings
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Supports issue batches, duplicate checks, and reviewed writes. Do not use for scans or fixes.
threat-model
Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.