From humanize
Consult Codex as an independent expert. Sends a question or task to codex exec and returns the response.
How this skill is triggered — by the user, by Claude, or both
Slash command
/humanize:ask-codex [--codex-model MODEL:EFFORT] [--codex-timeout SECONDS] [question or task][--codex-model MODEL:EFFORT] [--codex-timeout SECONDS] [question or task]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Send a question or task to Codex and return the response.
Send a question or task to Codex and return the response.
Do not pass free-form user text to the shell unquoted. The question or task may contain spaces or shell metacharacters such as (, ), ;, #, *, or [.
If the user only supplied a question or task, execute:
"${CLAUDE_PLUGIN_ROOT}/scripts/ask-codex.sh" "$ARGUMENTS"
If the user supplied flags such as --codex-model or --codex-timeout, reconstruct the command so those flags remain separate shell arguments and the remaining free-form question is passed as one quoted final argument.
Example:
"${CLAUDE_PLUGIN_ROOT}/scripts/ask-codex.sh" --codex-model gpt-5.4:high "Review the following round summary (M4)..."
Never run this unsafe form:
"${CLAUDE_PLUGIN_ROOT}/scripts/ask-codex.sh" $ARGUMENTS
because the shell will re-parse the question text and can fail before ask-codex.sh starts.
| Exit Code | Meaning |
|---|---|
| 0 | Success - Codex response is in stdout |
| 1 | Validation error (missing codex, empty question, invalid flags) |
| 124 | Timeout - suggest using --codex-timeout with a larger value |
| Other | Codex process error - report the exit code and any stderr output |
.humanize/skill/<timestamp>/output.md for referencegpt-5.4:high with a 3600-second timeoutnpx claudepluginhub lyken17/humanize --plugin humanize5plugins reuse this skill
First indexed Jul 14, 2026
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.