ask-codex

Send questions to Codex and output responses to stdout.

1.4k|123|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/PolyArch/humanize --skill ask-codex-polyarch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-codex
Source: https://github.com/PolyArch/humanize/tree/main/skills/ask-codex
Command: npx skills add https://github.com/PolyArch/humanize --skill ask-codex-polyarch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Consult Codex as an independent expert to obtain Codex responses to questions or tasks.

Core Features & Use Cases

  • Sends a question or task to Codex and returns the response.
  • Supports optional flags like --codex-model and --codex-timeout; reconstructs the command so those flags remain separate shell arguments.
  • Outputs Codex's response to stdout and status information to stderr. The default model is gpt-5.5:high with a 3600-second timeout.

Quick Start

Run the scripted command with your question and any optional flags, and read Codex's response from stdout.

Frequently Asked Questions about ask-codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query Codex from a shell script for code review?

You can query Codex from a shell script by running the command with your question, and the Skill returns the Codex response to stdout while sending status information to stderr.

What's the best way to automate deterministic Codex interactions for brainstorming?

Automating deterministic Codex interactions is done by executing the scripted command with your task, which preserves argument boundaries and outputs the response to stdout.

Can I specify a different model when consulting Codex as an independent expert?

Yes, you can specify a different model using the optional --codex-model flag when reconstructing the command, with the default model being gpt-5.5:high.

How do I prevent long-running Codex queries from hanging in my automation workflow?

You can prevent Codex queries from hanging by setting the optional --codex-timeout flag, which defaults to 3600 seconds, to limit the execution time.

Does this approach separate Codex response data from status logs for pipeline processing?

Yes, the approach separates Codex response data from status logs by writing the Codex response to stdout and emitting status information to stderr.

Are optional flags preserved as separate shell arguments when reconstructing commands?

Yes, optional flags such as --codex-model and --codex-timeout are preserved as separate shell arguments when the command is reconstructed.