init-codex-configlisted

Scaffold or migrate a project to use agent-harness from Codex. Use when applying agent-harness in Codex, converting Claude Code setup to AGENTS.md/.codex/.agents, or making a project ready for Codex skills and hooks without changing the original Claude setup.
jajupmochi/agent-harness · ★ 1 · AI & Automation · score 74

Install: claude install-skill jajupmochi/agent-harness

# init-codex-config Apply `agent-harness` to a project for Codex. This is the Codex counterpart to `setup/init-agent-config/SKILL.md`; read that source skill before adapting a project, then translate only the selected pieces into Codex surfaces. ## Preflight 1. Locate this repository. Prefer the current plugin root; otherwise check `~/.claude/agent-harness`. 2. Read: - `../../docs/CODEX_ADAPTATION_PLAN.md` - `../../INVENTORY.md` - `../../rules/README.md` - `../../setup/init-agent-config/SKILL.md` 3. Inspect the target project for existing `AGENTS.md`, `.codex/`, `.agents/skills`, `.claude/`, `CLAUDE.md`, package manifests, and Git status. 4. Do not edit `.claude/` or `CLAUDE.md` unless the user explicitly asks for Claude Code changes too. ## Decide the Codex surfaces - Durable project guidance goes in `AGENTS.md`, not `CLAUDE.md`. - Codex project hooks go in `.codex/hooks.json`. - Repo-scoped Codex skills go in `.agents/skills/<skill-name>/SKILL.md`. - User-wide Codex skills go in `~/.agents/skills`. - Reusable distribution goes through `.codex-plugin/plugin.json` and a marketplace entry. - MCP or app integrations belong in Codex MCP/app config, not in AGENTS.md. ## Questions If the user has not already provided answers, gather these decisions. In plan mode, use the available user-input tool. Outside plan mode, ask only the questions that affect file writes. 1. Project type: Python research, static site, frontend app, or custom. 2. Language p