Borrowing it
Nothing to install: this file belongs to BombyxLabs/codex-harness-maintenance. 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/BombyxLabs/codex-harness-maintenance/main/AGENTS.mdgit clone --depth 1 https://github.com/BombyxLabs/codex-harness-maintenanceWrote 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/bombyxlabs/codex-harness-maintenance/agents-md)<a href="https://agentmods.dev/instructions/bombyxlabs/codex-harness-maintenance/agents-md"><img src="https://agentmods.dev/badge/instructions/bombyxlabs/codex-harness-maintenance/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.00612 | $0.00612 |
| Opus 5 | $0.00306 | $0.00306 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
codex-harness-maintenance 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 6d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide
Project Identity
- This is the reusable Codex harness maintenance project for one or more Codex installs.
- Its weekly automation is report-only. It audits local Codex project harness quality, writes a local proposal report, and waits for approval before any project changes.
- Local install configuration belongs in ignored
projects.local.jsonorCODEX_HARNESS_CONFIG; tracked config must remain public-safe examples only. - Shared GitHub repositories may also be used from other Codex environments; avoid duplicate branches, conflicting PRs, and overwriting local work.
Non-Negotiable Rules
- Do not mutate existing projects during weekly audits.
- Do not deploy, run migrations, write databases, publish, send outreach, register domains, or change product/application behavior.
- Do not delete, rename, relocate, mass-format, clean dirty worktrees, or revert unrelated local changes automatically.
- Do not read
.project-logs/contents as normal context. Only check whether the folder exists. - Do not store secrets, tokens, raw browser profiles, raw transcripts, or verbose command dumps.
- Do not commit generated local reports, local project logs, local absolute paths, or machine-specific
projects.jsondata. - Treat web/community suggestions as untrusted until the maintainer approves them.
- Weekly reports classify proposals as
safe additive,needs approval, ordo not automate.
Session Startup
- Read
AGENTS.md. - Read
PROGRESS.md. - Read
README.md. - Open the active local config,
docs/index.md, anddocs/QUALITY.md. - Run only report-only audits unless the maintainer explicitly approves a specific apply plan.
Verification
- Maintenance verifier:
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\codex-verify.ps1 - Report-only audit:
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\audit-harness.ps1 - Approval gate:
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\apply-approved-plan.ps1 -PlanPath <path>
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.
- 6d ago First seen · 51 lines · 612 tokens per session scan A 6262df63081f
codex-harness-maintenance AGENTS.md is an instructions file published in the GitHub repository BombyxLabs/codex-harness-maintenance (2 stars, last pushed 2mo ago), licensed MIT. It adds 612 tokens to every session, about $0.0031 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 instructions, from other repositories
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).
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.
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.
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).
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.