finding-discovery Skill
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans. Published by openai in plugins.
Decision snapshot
Is this a fit?
Security review, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
19 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is finding-discovery Skill?
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Declared skill metadata
- Source file: plugins/codex-security/skills/finding-discovery/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use finding-discovery Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/codex-security/skills/finding-discovery/SKILL.md
What it does
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Skill instructions
Security Finding Discovery Objective Investigate the proposed code or code changes for technically plausible security vulnerabilities using the threat model as context. Artifact Resolution 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. SECURITY.md Guidance Gate Read ../../references/security-guidance.md and resolve the applicable policy before inspecting each source file. A delegated file-review worker must do the same before reading its assigned source. Code Diff Workflow If the scan target is for a targeted code-diff: - Read ../security-scan/references/scan-artifacts-and-ledger.md. - Generate rankinput.jsonl determ
Verified compatibility and discovery
Frequently asked questions
What is finding-discovery?
finding-discovery is a open-source AI agent skill with Copy skill directory. Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change.
Who is finding-discovery best for?
finding-discovery is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install finding-discovery?
Install or run finding-discovery using Copy skill directory. Check finding-discovery for the latest setup command.
Is finding-discovery actively maintained?
finding-discovery may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
