How do I install the Codex Exec Sub Agent skill?

Run npx skillmds@latest add chandeldivyam/codex-exec-sub-agent in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Codex Exec Sub Agent safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codex Exec Sub Agent?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codex Exec Sub Agent free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codex Exec Sub Agent?

chandeldivyam (@chandeldivyam) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codex Exec Sub Agent by chandeldivyam

Name: Codex Exec Sub Agent
Rating: 4.666666666666667 (3 reviews)
Author: chandeldivyam

Codex Exec Sub Agent

Delegate a task to a separate Codex process by running `codex exec --json` and logging the full JSONL event stream to a timestamped folder under `~/.codex/sub_agent_runs/`. Use when you want a lightweight “sub-agent” workflow where the main agent provides only a prompt, and the runner script handles run folders, prompt capture, and printing the JSONL path.

chandeldivyam Updated Sep 22, 2026

File contents

Run a sub-agent (Codex exec) and capture JSONL

Use the bundled runner script to avoid manually picking filenames/paths for the JSONL log.

Runner

Script: ~/.codex/skills/codex-exec-sub-agent/scripts/run.sh
Default runs dir: ~/.codex/sub_agent_runs/ (override with CODEX_SUBAGENT_RUNS_DIR)
Prints: the full path to run.jsonl as the last line on stdout

How to call

Important: when you ask a “main agent” to run this, configure that main agent’s timeout to at least ~10 minutes. Otherwise the parent may time out while the nested codex exec is still running (even though the sub-agent would eventually finish).

Pass the prompt via stdin (recommended for long prompts):

cat prompt.txt | ~/.codex/skills/codex-exec-sub-agent/scripts/run.sh

Or pass it as an argument (ok for short prompts):

~/.codex/skills/codex-exec-sub-agent/scripts/run.sh "Do X, then write results to /full/path/output.md"

How to think about the prompt

Treat the sub-agent prompt like a mini-brief:

Be explicit about the outcome: what “done” looks like.
Limit scope: what to include vs what to ignore.
Set output rules: format, length, tone, structure (especially if non-technical).
Prefer deterministic artifacts: if you want a file created/updated, tell it the full path.

Notes

Prefer full paths in prompts for any files you want created/updated.
The JSONL log is for inspection/debugging; treat the “real output” as a file path you instruct in the prompt.

Frequently asked questions