← ClaudeAtlas

codex-guidelisted

Use when configuring Codex hooks, plugins, skills, config layers, or managed requirements. Triggers on hooks.json, config.toml, requirements.toml, SessionStart, PreToolUse, PermissionRequest, SubagentStart, Stop, plugin-bundled hooks, hook trust hashes, concurrent commands, skipped prompt/agent handlers, or Codex guardrail coverage, even when the user doesn't say 'Codex hook'.
xonovex/platform · ★ 5 · AI & Automation · score 72
Install: claude install-skill xonovex/platform
# Codex Hooks and Guardrails Configure Codex's native hooks and guardrails without inventing unsupported guarantees or a universal hook file. ## Essentials - **Probe the release** - Record `codex --version` or an explicit not-installed result with the matrix snapshot. - **Use command handlers** - Only documented executing handler types can satisfy a capability. - **Reject parsed-only support** - Prompt, agent, and asynchronous command handlers are not executing release behavior in this snapshot. - **Scope the guardrail** - `PreToolUse` covers shell and unified exec, patch/edit/write, MCP, and most local function tools; hosted and specialized opt-out paths remain outside the guarantee. - **Preserve trust layers** - Non-managed definitions are hash-reviewed; managed hooks require separately distributed scripts. - **Transact native config** - Preview and verify hooks.json, config.toml, plugin, or requirements changes without replacing unrelated state. ## Gotchas - Only `type: command` executes in the documented snapshot; prompt and agent handlers are parsed but skipped. - The async option is parsed but asynchronous command hooks are skipped. - `PreToolUse` is a partial guardrail because hosted tools and specialized paths that opt out of the local function-tool hook path are not intercepted. - Matching command hooks start concurrently, so a denial cannot prevent another matching hook from starting. - `SubagentStart` can add context, but `continue: false` does not stop the su