Borrowing it
Nothing to install: this file belongs to ganimjeong/Harness-for-codex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ganimjeong/Harness-for-codex/main/AGENTS.mdgit clone --depth 1 https://github.com/ganimjeong/Harness-for-codexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/ganimjeong/harness-for-codex/agents-md)<a href="https://agentmods.dev/instructions/ganimjeong/harness-for-codex/agents-md"><img src="https://agentmods.dev/badge/instructions/ganimjeong/harness-for-codex/agents-md.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00687 | $0.00687 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
Harness-for-codex AGENTS.md 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 7d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Harness Instructions
This repository is a baseline workspace for Codex-driven implementation.
Commands
Run these from the repository root:
scripts/bootstrap
scripts/check
scripts/test
scripts/eval
scripts/doctor
scripts/hooks
scripts/bootstrap: prepare dependencies when a known stack is present.scripts/check: run lint, type checks, formatting checks, and tests when available.scripts/test: run only the test suite when available.scripts/eval: run the complete handoff verification sequence.scripts/doctor: report repository, tool, and environment readiness.scripts/hooks: install local Git hooks throughpre-commitwhen available.
Repository Layout
AGENTS.md: Codex instructions for this repo.CLAUDE.md: Claude Code bridge that importsAGENTS.md.README.md: Human-facing overview and workflow.harness.yml: Machine-readable harness metadata and command registry..devcontainer/: Optional reproducible development container..pre-commit-config.yaml: Optional local hook definitions.docs/: Project notes and decisions.scripts/: Stable automation entrypoints.tasks/: Task briefs and working notes.
Operating Principles
- Read the repository before editing. Prefer existing conventions over new ones.
- Keep changes scoped to the requested task.
- Do not revert user changes unless explicitly asked.
- Use
rgfor searching when available. - Use the standard scripts instead of one-off local commands when they cover the task.
- Add or update tests when behavior changes.
- Document decisions that affect future work in
docs/decisions.md. - Add nested
AGENTS.mdfiles in subdirectories only when that area needs different instructions. - Keep root-level agent instructions short and durable. Move long procedures into docs or scripts.
Task Loop
- Inspect: read relevant files and recent decisions.
- Plan: identify the narrow change and verification path.
- Implement: make focused edits.
- Verify: run
scripts/checkorscripts/eval. - Handoff: summarize changed files, verification, and residual risks.
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.
- 7d ago First seen · 85 lines · 687 tokens per session scan A 839a55b9971d
Harness-for-codex AGENTS.md is an instructions file published in the GitHub repository ganimjeong/Harness-for-codex (46 stars, last pushed 3mo ago), licensed MIT. It adds 687 tokens to every session, about $0.0034 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.