القائمة
Use when the user wants to list, inspect, or import ChatGPT-hosted Codex Security Cloud or Aardvark scan findings and accessible repos using local Codex ChatGPT credentials.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Triage this Framework Desktop's Hyprland, CachyOS, SDDM login, Ghostty/Chrome focus, workspace routing, Bluetooth, AirPods, PipeWire, media controls, and local desktop service incidents with live-state checks before changing config.
Triage this Framework Desktop's Hyprland, CachyOS, SDDM login, Ghostty/Chrome focus, workspace routing, Bluetooth, AirPods, PipeWire, media controls, and local desktop service incidents with live-state checks before changing config.
Create GitHub pull requests from the current checkout, including combined commit-and-PR requests. Use when Claude needs to inspect the change, use `draft-commit-message` as the source of truth for the commit message and PR title/body, then push and create a draft or ready PR without a separate wording approval when the user already requested PR creation.
Inspect, instrument, and control Linux Google Chrome through the local Codex Chrome Extension native messaging bridge. Use when Codex needs Chrome tabs, history, navigation, Chrome DevTools Protocol commands, native host manifest/socket troubleshooting, or a Linux browser-control path instead of Chrome DevTools MCP.
Create GitHub pull requests from the current checkout, including combined commit-and-PR requests. Use when Codex needs to inspect the change, use `draft-commit-message` as the source of truth for the commit message and PR title/body, then push and create a draft or ready PR without a separate wording approval when the user already requested PR creation.
Use the local linux-computer-use CLI or MCP server to inspect and safely interact with running Wayland/Hyprland desktop apps through Sky-compatible computer-use tools, grim screenshots, AT-SPI, wtype, ydotool, approvals, and dry-run raw input.
| name | codex-security-cloud |
| description | Use when the user wants to list, inspect, or import ChatGPT-hosted Codex Security Cloud or Aardvark scan findings and accessible repos using local Codex ChatGPT credentials. |
Use this skill to access the ChatGPT-hosted Codex Security Cloud findings UI data from a local Codex session.
This skill is an intake and query workflow. It does not discover new findings, triage security impact, validate exploitability, or fix code. Hand findings to the Codex Security skills for those later phases.
The cloud findings API uses the ChatGPT web access token that Codex stores for auth_mode chatgpt. It is not authenticated by OPENAI_API_KEY.
The helper reads the token from CODEX_ACCESS_TOKEN or from ~/.codex/auth.json, then calls the chatgpt.com Aardvark endpoints directly with Authorization bearer auth and a browser-style User-Agent header. It does not require Chrome, the Codex Chrome extension, browser cookies, or local storage.
If chatgpt.com returns a perimeter 403, retry with a fresher User-Agent via
CODEX_SECURITY_CLOUD_USER_AGENT or --user-agent. Do not add cookies or
browser automation unless the user explicitly asks for a separate fallback.
Do not print access tokens, refresh tokens, cookies, or local storage.
Run commands from the plugin root:
python3 scripts/codex_security_cloud.py doctor
python3 scripts/codex_security_cloud.py list-repos
python3 scripts/codex_security_cloud.py list-findings --repo buildbuddy-io/buildbuddy --limit 20
python3 scripts/codex_security_cloud.py get-finding 3e3cd14d62e08191a5af5494d13a30b1
For machine-readable output:
python3 scripts/codex_security_cloud.py list-findings --repo buildbuddy-io/buildbuddy --format json
Run doctor first when access has not been checked in the current session.
If doctor with --probe returns 403, retry with a current browser
User-Agent:
CODEX_SECURITY_CLOUD_USER_AGENT='Mozilla/5.0 ... Chrome/... Safari/537.36' python3 scripts/codex_security_cloud.py doctor --probe
Use list-repos to discover accessible repositories when the repo is unknown.
Use list-findings for the paginated queue. The list response contains lightweight items; finding titles are under commit_analysis.title.
Use get-finding with a hid for full details such as validation report, attack path analysis, proposed patch metadata, and relevant lines.
Observed same-origin endpoints:
GET /backend-api/aardvark/scan-findings
GET /backend-api/aardvark/scan-findings/{finding_id}
GET /backend-api/aardvark/scan-findings/list-accessible-repos
GET /backend-api/aardvark/scan-findings/list-authors
GET /backend-api/aardvark/scan_configurations
The 32-character IDs in the findings page URL are Aardvark finding hid values, not Codex Security MCP UUID scanId values.
When summarizing to the user: