Install
$ agentstack add skill-jajupmochi-agent-harness-init-codex-config ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
init-codex-config
Apply agent-harness to a project for Codex. This is the Codex counterpart to setup/init-agent-harness/SKILL.md; read that source skill before adapting a project, then translate only the selected pieces into Codex surfaces.
Preflight
- Locate this repository. Prefer the current plugin root; otherwise check
~/.claude/agent-harness.
- Read:
../../docs/CODEX_ADAPTATION_PLAN.md../../INVENTORY.md../../rules/README.md../../setup/init-agent-harness/SKILL.md
- Inspect the target project for existing
AGENTS.md,.codex/,
.agents/skills, .claude/, CLAUDE.md, package manifests, and Git status.
- Do not edit
.claude/orCLAUDE.mdunless the user explicitly asks for
Claude Code changes too.
Decide the Codex surfaces
- Durable project guidance goes in
AGENTS.md, notCLAUDE.md. - Codex project hooks go in
.codex/hooks.json. - Repo-scoped Codex skills go in
.agents/skills//SKILL.md. - User-wide Codex skills go in
~/.agents/skills. - Reusable distribution goes through
.codex-plugin/plugin.jsonand 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.
- Project type: Python research, static site, frontend app, or custom.
- Language policy: English, Chinese, bilingual, or leave unchanged.
- Context tags:
always,research-pkg,ui-project,static-site,
ml-research, web-perf, image-or-video-work, docs-site, electron-or-desktop.
- Which personal rules to include: output brevity, tool proactivity,
no reread, writing style, human-readable output, autorun mode.
- Skill scope: repo
.agents/skillsor user~/.agents/skills. - Hook scope: project
.codex/hooks.json, user~/.codex/hooks.json, or no hooks. The tested local activation uses user hooks; do not also declare plugin hooks or the same command can run twice.
When the user says autorun, choose conservative defaults and continue unless a file overwrite, dependency install, network call, or destructive operation needs approval.
Compose for Codex
- Preserve any existing
AGENTS.md; merge additively or create
AGENTS.md.bak. before replacing.
- Generate
AGENTS.mdwith concise instructions. Do not paste the full rule
library. Include references to selected source rule files, for example: Rules source: ~/.claude/agent-harness/rules/phased-planning/RULE.md.
- If project hooks are selected, create
.codex/hooks.jsonfrom this repository's root
hooks.json, then rewrite every command to a stable absolute or git-root-based path. The root file is a source template, not an automatically discovered plugin hook.
- If repo skills are selected, copy the relevant top-level Codex wrapper
skill directories from this repository into .agents/skills/.
- If a template is selected, use the corresponding template directory as a
source, but translate Claude-specific files:
CLAUDE.template.md-> summarizedAGENTS.md.claude/settings.template.json->.codex/hooks.json.claude/skills->.agents/skills
- Add a short README note only when the project already has a README and the
user wants provenance recorded.
Verification
Run checks proportional to the files written:
jq emptyon every JSON file created or changed.python3 -c 'import tomllib; ...'for TOML files if present.rg -n "CLAUDE|\\.claude" AGENTS.md .codex .agentsto ensure Codex files do
not accidentally claim to be Claude configuration, except in provenance text.
git status --shortto report changed files.
Do not claim that hooks or skills are active in the current Codex task until they have been installed in a discovered location and a real lifecycle event or explicit invocation proves that task picked them up. Trusting a hook definition does not prove an already-running task rebuilt its lifecycle registry.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jajupmochi
- Source: jajupmochi/agent-harness
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.