Skip to main content
skill CX Codex official · OpenAI

security-scan · openai — Claude Code skill: audit and install

The security-scan Claude Code skill checks a repository or selected paths for exploitable vulnerabilities. It audits the current source in one pass, rather than reviewing a set of changes.

Apache-2.0 157 installs ★ 14,254 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add openai/codex-security --skill security-scan -a claude-code
Open on GitHub

What security-scan does

The skill traces untrusted input through the code to the operation it can affect. It checks where access is enforced and, for exposed credentials, who can read them and what permissions they grant.

The review reads the current source offline and does not modify the target. Findings include source lines and concrete impact; the report also records reviewed areas and open questions. Use diff for PR, commit, branch, or working-tree changes. deep handles a scan explicitly requested as in-depth.

What it helps with

  • find exploitable flaws across a repository
  • audit selected source paths
  • trace untrusted input to the operation it controls
  • check who can read an exposed credential and what access it grants

Example prompts for the agent

  • Audit the current repository for security vulnerabilities.
  • Check src/auth and src/api for exploitable flaws.
  • Trace how input from src/upload affects file operations.

How to install security-scan

1Skills CLI (Vercel)

npx skills add openai/codex-security --skill security-scan -a claude-code

2Manually: put the files in place

~/.claude/skills/security-scan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/security-scan/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about security-scan

How do I install security-scan in Claude Code?

Run npx skills add openai/codex-security --skill security-scan -a claude-code. The skill file is located at ~/.claude/skills/security-scan/SKILL.md.

What does security-scan do?

It audits the current source in a whole repository or selected paths, looking for vulnerabilities an attacker could exploit.

How does security-scan differ from diff and deep?

security-scan audits the current code. Use diff for PR, commit, branch, or working-tree changes; deep is for an explicitly requested in-depth scan.

Source text

SKILL.md · Apache-2.0
---
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."
---

# 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](../../references/core-scan.md) 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](references/scan-results.md) 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](../../references/access-advisory.md) only when directed at launch, and begin the source review. Use [managed scan progress](references/managed-scan.md) 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](../../references/investigation-time-budget.md) 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](references/scan-results.md). 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.

© openai · Apache-2.0 · openai/codex-security

Similar skills

All skills for Security →

security-scan by other authors comes first.

security-scan affaan-m security-scan scans the .claude/ directory for leaked secrets, loose permissions and hook injection risks. Useful right after you edit settings.json or add an MCP server. CX Codex +1 6,500installs security-scan ruvnet security-scan scans a repo at three depths: dependency audit, hard-coded secrets, risky code patterns. Useful before a release or while reviewing a PR. CX Codex +1 748installs security-scan codewithmukesh security-scan is a Claude Code skill for static audits of .NET projects across six layers: packages, secrets, OWASP patterns, auth, CORS and data protection. Findings include severity and fix code. CX Codex +1 4,000installs security-scan jwynia security-scan scans a codebase for OWASP Top 10 flaws, hardcoded credentials and unsafe configs. Useful before a deploy or when reading unfamiliar code. CX Codex +1 497installs eastsword-dfyx-code-security-review reason-machines The eastsword-dfyx-code-security-review skill runs white-box security audits by tracking data flows and spotting authorization or injection flaws. It suits projects preparing code for production. CX Codex +1 331installs ghost-validate ghostsecurity ghost-validate validates security vulnerability findings by tracing code paths and checking live endpoints. Separates true positive security bugs from scanner false positives. CX Codex +1 4,200installs ghost-scan-code ghostsecurity ghost-scan-code is a Claude Code skill that plans targeted source-code security scans. It runs for requests to audit an application or library for vulnerabilities. CX Codex +1 5,700installs vuln-scan official anthropics vuln-scan is a Claude Code skill that statically scans source code for vulnerabilities and writes findings to JSON and markdown for triage. CX Codex +1 1,200installs web-security-review OWASP web-security-review audits web applications against OWASP Top 10 (2021) risks and produces a prioritized remediation roadmap. Useful for reviewing server code, framework setups, and web configurations. CX Codex +1 881installs skill-file-security reason-machines skill-file-security adds OWASP and CWE security rule sets to your project so your AI assistant can audit code and prepare patch diffs right inside your editor. CX Codex +1 784installs

From the same set4

Project sponsors

Companies that keep this analytics open