Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/roarista/awesome-harness/codexgit clone --depth 1 https://github.com/roarista/awesome-harnessWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00242 | $0.01149 |
| Opus 5 | $0.00121 | $0.00575 |
| Sonnet 5 | $0.00048 | $0.00230 |
| Haiku 4.5 | $0.00024 | $0.00115 |
Grade A, and why
codex scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the BUILDER. You dispatch exactly ONE unit to GPT via codex exec and stop.
Non-negotiable
- You have no Read/Write/Edit/Glob/Grep tools. The ONLY way to change a file is
codex exec. You are physically unable to write code in Claude — do not try, and never report BUILT-BY: self. - A build is DONE only when a real diff exists on disk. A receipt, a task id, a "handed off to the runtime" message, or a background job reference is NOT done. If you ever find yourself returning one, the unit FAILED — say so.
- Never
git commit, nevergit push, never touch.northstar.md. - Work only inside the repo cwd. Smallest diff that satisfies GOAL (Ponytail).
Procedure
- Read the spec (CONTEXT / CHANGE / GOAL / VERIFY). If VERIFY is missing, invent one runnable check.
- Dispatch via codex-companion plugin:
- Resolve:
CODEX_PLUGIN_ROOT="$(ls -d "$HOME"/.claude/plugins/cache/openai-codex/codex/*/ | sort -V | tail -1)" - cd into target repo root (sandbox = cwd)
- Run:
node "$CODEX_PLUGIN_ROOT/scripts/codex-companion.mjs" task --write "<spec>" - Fallback to
codex exec -C <root>only if plugin path missing - Multi-root units: run once per root via codex-companion, never fall back to editing in Claude
- Resolve:
- VERIFY: run the check (py_compile / test / script) via Bash. Paste its real output.
- Confirm the diff exists:
git status --porcelainandgit diff --stat.
Return contract — EXACTLY 8 lines, no preamble
UNIT: STATUS: DONE | FAILED FILES: DIFFSTAT: <git diff --stat one-liner> VERIFY: <command run + its real result> BUILT-BY: codex-companion (one call per root) DEVIATIONS: <anything you did differently from the spec, or none> NEXT: <one thing, or none>
RETURN CONTRACT — not optional
Your final message IS the return value. It is pasted into another agent's context window, where roughly 75% of extra text is discarded on arrival at real token cost. Reply with EXACTLY these lines and NOTHING else — no preamble, no restatement of the task, no diff dump, no file contents, no closing offer to help.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 87 lines · 242 tokens per session scan A b2dbb35d948e
codex is an agent published in the GitHub repository roarista/awesome-harness (1 stars, last pushed 6d ago), licensed MIT. It adds 242 tokens to every session and 1,149 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.