codex-subagent▌
am-will/codex-skills · updated May 19, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Spawn autonomous subagents to offload context-heavy work and preserve parent token budget.
- ›Subagents burn their own tokens and return only final results, ideal for deep research (3+ searches), codebase exploration (8+ files), multi-step workflows, and long-running operations
- ›Choose between mini model (gpt-5.1-codex-mini) for pure search tasks or inherit parent model for multi-step analysis, refactoring, and generation work
- ›Supports up to 5 parallel subagents via background shell exec
Codex Subagent Skill
Spawn autonomous subagents to offload context-heavy work. Subagents burn their own tokens, return only final results.
Golden Rule: If task + intermediate work would add 3,000+ tokens to parent context → use subagent.
Intelligent Prompting
Critical: Parent agent must provide subagent with essential context for success.
Good Prompting Principles
- Include relevant context - Give the subagent thorough context
- Be specific - Clear constraints, requirements, output format
- Provide direction - Where to look, what sources to prioritize
- Define success - What constitutes a complete answer
Examples
❌ Bad: "Research authentication"
✅ Good: "Research authentication in this Next.js codebase. Focus on: 1) Session management strategy (JWT vs session cookies), 2) Auth provider integration (NextAuth, Clerk, etc), 3) Protected route patterns. Check /app, /lib/auth, and middleware files. Return architecture summary with code examples."
❌ Bad: "Search for Codex SDK"
✅ Good: "Find the most recent Codex SDK documentation and summarize key updates. Focus on: 1) Installation/quickstart, 2) Core API methods and parameters, 3) Breaking changes or deprecations. Prioritize official OpenAI docs and release notes. Return a concise summary with citations."
❌ Bad: "Find API endpoints"
✅ Good: "Find all REST API endpoints in this Express.js app. Look in /routes, /api, and /controllers directories. For each endpoint document: method (GET/POST/etc), path, auth requirements, request/response schemas. Return as markdown table."
Prompting Template
[TASK CONTEXT]
You are researching/analyzing [SPECIFIC TOPIC] in [LOCATION/CODEBASE/DOMAIN].
[OBJECTIVES]
Your goals:
1. [1st objective with specifics]
2. [2nd objective]
3. [3rd objective if needed]
[CONSTRAINTS]
- Focus on: [specific areas/files/sources]
- Prioritize: [what matters most]
- Ignore: [what to skip]
[OUTPUT FORMAT]
Return: [exactly what format parent needs]
[SUCCESS CRITERIA]
Complete when: [specific conditions met]
Model Selection
Use Mini Model (gpt-5.1-codex-mini + medium)
Pure search only - no additional work after gathering info.
Bash (Linux/macOS)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check \
-m gpt-5.1-codex-mini -c 'model_reasoning_effort="medium"' \
"Search web for [TOPIC] and summarize findings"
PowerShell (Windows)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check `
-m gpt-5.1-codex-mini -c 'model_reasoning_effort="medium"' `
"Search web for [TOPIC] and summarize findings"
Inherit Parent Model + Reasoning
Multi-step workflows - search + analyze/refactor/generate:
Bash (Linux/macOS)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check \
-m "$MODEL" -c "model_reasoning_effort=\"$REASONING\"" \
"Find auth files THEN analyze security patterns and propose improvements"
PowerShell (Windows)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check `
-m $MODEL -c "model_reasoning_effort=`"$REASONING`"" `
"Find auth files THEN analyze security patterns and propose improvements"
Decision Logic
Is task PURELY search/gather?
├─ YES: Any work after gathering?
│ ├─ NO → mini model
│ └─ YES → inherit parent
└─ NO → inherit parent
Basic Usage
Bash (Linux/macOS)
# Get parent session settings (respects active profile; falls back to top-level)
# NOTE: codex-parent-settings.sh prints two lines; use mapfile to avoid empty REASONING.
mapfile -t _settings < <(scripts/codex-parent-settings.sh)
MODEL="${_settings[0]}"
REASONING="${_settings[1]}"
# Spawn subagent (inherit parent)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check \
-m "$MODEL" -c "model_reasoning_effort=\"$REASONING\"" \
"DETAILED_PROMPT_WITH_CONTEXT"
# Safer prompt construction (no backticks / command substitution)
PROMPT=$(cat <<'EOF'
[TASK CONTEXT]
You are analyzing /path/to/repo.
[OBJECTIVES]
1. Do X
2. Do Y
[OUTPUT FORMAT]
Return: path - purpose
EOF
)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check \
-m "$MODEL" -c "model_reasoning_effort=\"$REASONING\"" \
"$PROMPT"
# Pure search (use mini)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check \
-m gpt-5.1-codex-mini -c 'model_reasoning_effort="medium"' \
"SEARCH_ONLY_PROMPT"
# JSON output for parsing
codex exec --dangerously-bypass-approvals-and-sandbox --json "PROMPT" | jq -r 'select(.event=="turn.completed") | .content'
PowerShell (Windows)
# Get parent session settings (respects active profile; falls back to top-level)
$scriptPath = Join-Path $env:USERPROFILE ".codex\skills\codex-subagent\scripts\codex-parent-settings.ps1"
$settings = & $scriptPath
$MODEL = $settings[0]
$REASONING = $settings[1]
# Spawn subagent (inherit parent)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check `
-m $MODEL -c "model_reasoning_effort=`"$REASONING`"" `
"DETAILED_PROMPT_WITH_CONTEXT"
# Use here-string for multi-line prompts (avoids escaping issues)
$PROMPT = @'
[TASK CONTEXT]
You are analyzing /path/to/repo.
[OBJECTIVES]
1. Do X
2. Do Y
[OUTPUT FORMAT]
Return: path - purpose
'@
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check `
-m $MODEL -c "model_reasoning_effort=`"$REASONING`"" `
$PROMPT
# Pure search (use mini)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check `
-m gpt-5.1-codex-mini -c 'model_reasoning_effort="medium"' `
"SEARCH_ONLY_PROMPT"
# Method 1 (Recommended): Use -o to output directly to file
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check `
-m $MODEL -c "model_reasoning_effort=`"$REASONING`"" `
-o output.txt "PROMPT"
$content = Get-Content -Path output.txt -Raw
# Method 2: Parse JSONL event stream
$jsonl = codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check --json "PROMPT"
$events = $jsonl -split "`n" | Where-Object { $_ } | ForEach-Object { $_ | ConvertFrom-Json }
$content = $events |
Where-Object -Property type -EQ "item.completed" |
Where-Object { $_.item.type -eq "agent_message" } |
Select-Object -ExpandProperty item |
Select-Object -ExpandProperty text
Parallel Subagents (Up to 5)
Spawn multiple subagents for independent tasks:
Bash (Linux/macOS)
# Research different topics simultaneously
codex exec --dangerously-bypass-approvals-and-sandbox -m "$MODEL" -c "model_reasoning_effort=\"$REASONING\"" "Research topic A..." &
codex exec --dangerously-bypass-approvals-and-sandbox -m "$MODEL" -c "model_reasoning_effort=\"$REASONING\"" "Research topic B..." &
wait
PowerShell (Windows)
Use PowerShell Jobs for parallel execution with -o to output to separate files:
# Parallel execution with file output
$job1 = Start-Job -ScriptBlock {
param($m, $r, $out)
codex exec --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check `
-m $m -c "model_reasoning_effort=`"$r`"" -o $out "Research topic A..."
} -ArgumentList $MODEL, $REASONING, how to use codex-subagentHow to use codex-subagent on Cursor
AI-first code editor with Composer
1Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add codex-subagent
2Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/am-will/codex-skills --skill codex-subagentThe skills CLI fetches codex-subagent from GitHub repository am-will/codex-skills and configures it for Cursor.
3Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?││ ── Universal (.agents/skills) ── always included ────│ • Amp│ • Antigravity│ • Cline│ • Codex│ ●Cursor(selected)│ • Cursor│ • Windsurf4Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/codex-subagentReload or restart Cursor to activate codex-subagent. Access the skill through slash commands (e.g., /codex-subagent) or your agent's skill management interface.
⚠Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
Additional Resources
List & Monetize Your Skill
Submit your Claude Code skill and start earning
GET_STARTED →Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
✓Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
✓Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
general reviewsRatings
4.5★★★★★68 reviews- ★★★★★James Haddad· Dec 28, 2024
Useful defaults in codex-subagent — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Tariq Agarwal· Dec 24, 2024
We added codex-subagent from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kwame Agarwal· Dec 20, 2024
codex-subagent fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kwame Bansal· Dec 16, 2024
Registry listing for codex-subagent matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Chaitanya Patil· Dec 12, 2024
codex-subagent fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Advait Chen· Dec 12, 2024
I recommend codex-subagent for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Xiao White· Dec 4, 2024
codex-subagent fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Min Martin· Nov 23, 2024
Registry listing for codex-subagent matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Zara Wang· Nov 15, 2024
codex-subagent reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Olivia Thomas· Nov 11, 2024
Useful defaults in codex-subagent — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 68
1 / 7