Track Findings: purpose and common use cases
Track Findings is cataloged from the official OpenAI Plugins repository as a skill bundled with the codex-security plugin. Artifiner verified its source at plugins/codex-security/skills/track-findings/SKILL.md against repository revision 1e285826e604; the page is classified under Security from source-backed metadata rather than generated ratings or reviews.
Where Track Findings fits in an agent workflow
Track Findings is a Codex skill for security workflows. Track Findings's role is practical rather than generic: it gives an agent task-specific instructions for identifying and validating software risk. In the catalog it is discoverable around track, findings, and security, which are useful starting points when the user knows the outcome they need but not the exact capability name. Track Findings is bundled with the codex-security plugin, so it should be understood as one capability inside that broader integration rather than as a separate application.
What to check before using Track Findings
Use Track Findings when the job maps to security review, validation and defensive engineering. For Track Findings, a sensible workflow is to start with the task, check that the skill matches the project and tools involved, and then follow the upstream instructions rather than treating the directory description as executable documentation. Artifiner keeps the Track Findings source link visible so you can inspect its current SKILL.md before relying on behavior that may change as the repository evolves.
Codex Security workflow for track findings, supporting a defined stage of repository security analysis, policy, findings, or validation.