القائمة
This skill should be used when configuring Codex CLI, setting up profiles, or when config.toml, sandbox mode, Codex config, or approval policy are mentioned.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Patterns for @outfitter/daemon including lifecycle management, IPC communication, health checks, and PID files. Use when building background services, daemons, or when "daemon", "IPC", "health check", "background service", or "@outfitter/daemon" are mentioned.
Creates handlers, CLI commands, MCP tools, and daemon services following Outfitter Dev Kit conventions. Use when adding new components to a project, scaffolding code, or when "create handler", "new command", "add tool", or "daemon service" are mentioned.
Deep patterns for @outfitter/mcp including tool registration, Zod schemas, resources, and server configuration. Use when building MCP servers, registering tools, defining resources, or when "MCP server", "MCP tool", "registerTool", or "@outfitter/mcp" are mentioned.
Generates patterns, templates, and guides for @outfitter/* packages. Covers transport-agnostic handler systems, Result types, error taxonomy, and package APIs. Use when working with @outfitter/*, Result types, Handler contract, error taxonomy, or when Result, Handler, ValidationError, NotFoundError, OutfitterError, or package names like contracts, cli, mcp, schema, tui, daemon, config, logging are mentioned.
Verify Outfitter compliance in a codebase. Scans for anti-patterns (throws, console, hardcoded paths) and produces a severity-ranked compliance report. Use for pre-commit checks, code review, or migration validation.
Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.
| name | codex-config |
| description | This skill should be used when configuring Codex CLI, setting up profiles, or when config.toml, sandbox mode, Codex config, or approval policy are mentioned. |
| metadata | {"version":"1.0.1","related-skills":["claude-craft","skillcraft"]} |
Manages configuration files for OpenAI Codex CLI, including model settings, sandbox policies, MCP servers, and profiles.
Primary Config: ~/.codex/config.toml
Skills Paths (precedence, highest first):
$CWD/.codex/skills/ - Current directory$CWD/../.codex/skills/ - Parent directory$REPO_ROOT/.codex/skills/ - Repository root~/.codex/skills/ - User-level/etc/codex/skills/ - System/admin level# Model settings
model = "gpt-5.2-codex"
model_verbosity = "medium" # high | medium | low
model_reasoning_effort = "high" # low | high | xhigh
# Permissions
approval_policy = "on-failure" # untrusted | on-failure | on-request | never
sandbox_mode = "workspace-write" # read-only | workspace-write | danger-full-access
exec_timeout_ms = 300000 # 5 minutes
# Misc
file_opener = "cursor" # Editor for opening files
Define named profiles for different workflows:
[profiles.max]
model = "gpt-5.1-codex-max"
model_verbosity = "high"
model_reasoning_effort = "xhigh"
[profiles.fast]
model = "gpt-5.1-codex-mini"
model_verbosity = "low"
model_reasoning_effort = "low"
Usage:
codex -p max "complex refactoring task"
codex -p fast "quick fix"
[mcp_servers.server-name]
command = "npx"
args = ["-y", "@package/mcp-server"]
enabled = true
tool_timeout_sec = 60.0
[mcp_servers.server-name.env]
API_KEY = "your-key"
# Explicit invocation
codex "$plan implement authentication"
codex "$skill-creator new skill for testing"
# Implicit (Codex decides based on context)
codex "plan out the implementation"
$plan - Research and create implementation plans$skill-creator - Bootstrap new skills$skill-installer - Download skills from GitHubOverride any config value at runtime:
codex -c model="o3"
codex -c 'sandbox_permissions=["disk-full-read-access"]'
codex -c shell_environment_policy.inherit=all
| Flag | Equivalent |
|---|---|
--full-auto | -a on-request --sandbox workspace-write |
--oss | -c model_provider=oss (local LM Studio/Ollama) |
--search | Enable web search tool |
codex --full-auto "implement feature"
codex -C /path/to/project "work in different dir"
codex --add-dir /additional/path "access multiple dirs"
# Check TOML syntax
cat ~/.codex/config.toml | toml-lint
# Test config override
codex -c model="test" --help
# Verify MCP servers
codex mcp list
Config not loading: Verify ~/.codex/config.toml exists, check TOML syntax
MCP server not connecting: Check command path, verify API keys, check enabled = true
Skills not found: Verify path hierarchy, check SKILL.md exists in skill folder
Sandbox too restrictive: Use -s workspace-write, check project trust level
Detailed documentation for specific scenarios: