Answer: Copy the pull-request workflow to `.github/workflows/codex-security-pr.yml`, replacing `REPLACE_WITH_REVIEWED_COMMIT` with `a98b35d7eef9f85c298c86229445bb64ac427aaf`, then choose a model your API key can access. The template sets a $5 threshold for estimated scan costs and fails on high or critical findings; for advisory findings, set `fail-on-severity: none`. Status: Confirmed Entry: tool/codex/integrations/scan-pull-request-changes Revision: 1 Digest: sha256:11a6f15b7c67b0b0 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:03Z Last changed: 2026-11-13T03:53:03Z Last verified: 2026-11-20T13:41:35Z Next check: 2026-11-21T13:41:35Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of workflow file path | .github/workflows/codex-security-pr.yml | | [1] | 2026-11-20 distribution commit | a98b35d7eef9f85c298c86229445bb64ac427aaf | | [1] | 2026-11-20 action version | action-v0.9.1 | | [1] | 2026-11-20 cost threshold | $5 | USD | [1] | 2026-11-20 advisory setting | fail-on-severity: none | | [1] | 2026-11-20 Dependabot secret name | CODEX_SECURITY_API_KEY | | [1] | 2026-11-20 Sources: [1] OpenAI. "Run Codex Security in GitHub Actions". https://learn.chatgpt.com/docs/security/cli/ci/github.md Role: primary. Accessed: 2026-11-20T13:41:35Z Quote: "to `.github/workflows/codex-security-pr.yml`" (Supports: workflow file path) Quote: "`REPLACE_WITH_REVIEWED_COMMIT` with `a98b35d7eef9f85c298c86229445bb64ac427aaf`" (Supports: distribution commit) Quote: "the distribution commit for `action-v0.9.1`" (Supports: action version) Quote: "The template sets a $5 threshold for estimated" (Supports: cost threshold) Quote: "For advisory findings, set `fail-on-severity: none`." (Supports: advisory setting) Quote: "also save `CODEX_SECURITY_API_KEY` as a" (Supports: Dependabot secret name) Snapshot SHA-256: 888cc3aa1b06e72f841c1ac8e201b76e37e0cab0f271a9c0421448ba14709e5e (captured 2026-11-13T03:53:03Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:53:03Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:41:35Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:41:35Z Last attempt: 2026-11-20T13:41:35Z Notes and limitations: Extracted automatically from a single official source (section "Scan pull-request changes"). Related: https://latestn.com/tool/codex/integrations/set-up-codex-amazon-bedrock How do I set up Codex to use Amazon Bedrock as its model provider? https://latestn.com/tool/codex/integrations/set-up-linear-integration How do I set up the Codex integration in Linear? https://latestn.com/tool/codex/integrations/setup-automatic-codex-review How do I set up automatic Codex code reviews for a GitHub pull request? https://latestn.com/tool/codex/integrations/publish-draft-merge-request How do I publish a draft merge request with Codex Security fixes in GitLab? https://latestn.com/tool/codex/integrations/request-codex-review-gitlab-mr How do I request a Codex review on a GitLab merge request? https://latestn.com/tool/codex/integrations/save-reports-upload-sarif How do I save Codex Security reports and upload SARIF in GitHub Actions? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:53:03Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/integrations/scan-pull-request-changes/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/integrations/scan-pull-request-changes POST: https://latestn.com/dispute/tool/codex/integrations/scan-pull-request-changes with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/integrations/scan-pull-request-changes?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I set up a Codex Security workflow to scan pull-request changes in GitHub Actions? Revision 1, last verified 2026-11-20T13:41:35Z. https://latestn.com/tool/codex/integrations/scan-pull-request-changes (accessed 2026-11-21T09:50:37Z). @misc{LatestN_tool_codex_integrations_scan_pull_request_changes_r1, title = {How do I set up a Codex Security workflow to scan pull-request changes in GitHub Actions?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/integrations/scan-pull-request-changes}}, note = {Revision 1; digest sha256:11a6f15b7c67b0b0; last verified 2026-11-20T13:41:35Z; accessed 2026-11-21T09:50:37Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/integrations/scan-pull-request-changes