# Codex Harness Bootstrap > Install or refresh Codex custom-agent TOML profiles and the minimal AGENTS.md loader block for the coding-agent orchestration harness. Use when this capability is needed. - Skill: `tomevault-io/codex-harness-bootstrap` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/codex-harness-bootstrap` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/codex-harness-bootstrap/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/codex-harness-bootstrap --- # Codex harness bootstrap Use this skill when setting up the coding-agent orchestration harness for Codex. Run the canonical bootstrap script from the installed plugin location: ```bash python /path/to/coding-agent-orchestration-harness/skills/codex-harness-bootstrap/scripts/install_codex_harness.py ``` The script asks whether to install the agents in user scope or repository scope. Use `--scope user` to install into `~/.codex/agents/`. Use `--scope repo` to install into `.codex/agents/` under the nearest repository root. Use `--repo-root` with `--scope repo` when installing into a repository other than the current working directory's nearest `.git` parent. Use `--overwrite-agents` to replace existing profiles. `--overwrite` is also accepted. Use `--dry-run` to print planned writes/skips without creating directories or writing files. Use `--check` to compare installed files against source templates and report `MATCH`, `MISSING`, `INVALID`, `MISSING_SOURCE`, or `STALE_OR_MODIFIED`. A successful check also requires the managed install manifest to exist as a file. Use `--verify` to assert required installed files and the managed manifest exist. With user scope, pair with `--user-instructions add` when the managed `AGENTS.md` loader block should also be required. Normal installs write a managed `.coding-agent-orchestration-harness-install.json` manifest in the target agents directory by default. Use `--no-write-manifest` only when manifest creation is intentionally unwanted. When installing in user scope, the script also asks whether to add a small managed harness routing block to `~/.codex/AGENTS.md`. - Existing content is never overwritten wholesale. - If `AGENTS.md` already has other content, review the preview and choose whether to append the managed block. - If the managed block already exists, choose whether to replace only that block. - Use `--user-instructions add` for non-interactive add/update, or `--user-instructions skip` to leave `AGENTS.md` untouched. The managed `AGENTS.md` block is loader-only. It routes Codex to `$orchestration-harness`; workflow mechanics stay in the skill. --- > Source: [ebigunso/agent-harness](https://github.com/ebigunso/agent-harness) — distributed by [TomeVault](https://tomevault.io).