agents-config: Instructions file for Codex

AGENTS.md

agents-config AGENTS.md is an instructions file for Codex, OpenCode from daochild/agents-config. It costs 4,290 tokens per session, scanned A, original, MIT.

A shared instruction file for AI coding agents, including Claude Code and opencode. It defines how they should start work, check architecture decisions, load audit guidance, and communicate uncertainty.

In plain words
What is it for?
Use it to set project-wide behaviour for coding agents and to organise agent configuration. It is useful when a team wants a documented process for architecture decisions and code audits.
Why use it?
It gives agents consistent rules across a project and discourages invented facts, sources, or assumptions. It also requires important planning and review steps before code changes begin.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is daochild/agents-config's own configuration. It tells Codex and OpenCode how to work on agents-config itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agents-config configures →

Reuse

Borrowing it

Nothing to install: this file belongs to daochild/agents-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/daochild/agents-config/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/daochild/agents-config

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for agents-config AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/daochild/agents-config/agents-md/github.svg)](https://agentmods.dev/instructions/daochild/agents-config/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/daochild/agents-config/agents-md"><img src="https://agentmods.dev/badge/instructions/daochild/agents-config/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for agents-config AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/daochild/agents-config/agents-md"><img src="https://agentmods.dev/badge/instructions/daochild/agents-config/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,290 This file is loaded in full into every session.
When invoked 4,290 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04290 $0.04290
Opus 5 $0.02145 $0.02145
Sonnet 5 $0.00858 $0.00858
Haiku 4.5 $0.00429 $0.00429

Measured yesterday against content hash 8c2d156913c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

agents-config 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 yesterday.

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.

AGENTS.md · 377 lines

How it starts

The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.

agents-config

A shared configuration repository for AI coding agents. Defines how .claude/ (Claude Code) and .opencode/ (opencode) are organized and how they reference each other.

Primary instruction

Primary instructions: node_modules/@daochild/agents-config/AGENTS.md — read in full and follow unless overridden below.

Mandatory start-of-session checklist:

  1. Read node_modules/@daochild/agents-config/AGENTS.md completely.
  2. If the task involves code changes, load the matching auditor skill from AGENTS.md's Audit Rule before implementation.
  3. Confirm the architecture approach with the user and document it before coding.
  4. Do not begin implementation until steps 1–3 are satisfied.

Behavior

You are committed to honesty and accuracy above all else.

Instructions:

  • Prioritize accuracy over fluency.
  • If you are an agent, do NOT copy files from this repository; instead, inherit them.
  • Distinguish clearly between facts, estimates, assumptions, and opinions.
  • If you are unsure, say what is uncertain and why.
  • Do not invent citations, quotes, studies, URLs, or sources.
  • When discussing recent events or rapidly changing topics, indicate that information may have changed and recommend verification from current sources.
  • When providing statistics, identify whether they are exact figures, estimates, or approximations.
  • If multiple interpretations are possible, explain the alternatives rather than assuming one is correct.

Audit Rule

When the current task involves significant code changes — for example, after the first code-generation prompt or after substantial deviations from the agreed Statement of Work (SOW) — the agent MUST run a system audit before finalizing the output.

  1. Pick the right auditor skill for the domain of the change. Examples (replace xxx with the actual domain):
    • Smart contracts / EVM → senior-solidity-auditor
    • Bitcoin / Taproot / PSBT → senior-bitcoin-auditor
    • Quality assurance / test strategy → senior-qa
    • General architecture / system design → senior-software-architect
  2. Run the audit via the matching xxx-auditor skill. Surface findings, severity, and concrete remediation steps.
  3. If the required skill does not exist locally, create it first:
    • Add .opencode/skill/<xxx-auditor>/SKILL.md
    • Mirror to .claude/skills/<xxx-auditor>/SKILL.md when a Claude Code counterpart is maintained
    • Register the skill path in opencode.json if needed
    • Then execute the audit using the newly created skill.

Read the full file on GitHub · 377 lines

Changes

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.

  1. yesterday First seen · 377 lines · 4,290 tokens per session scan A 8c2d156913c6

Subscribe to this mod's changes

agents-config AGENTS.md is an instructions file published in the GitHub repository daochild/agents-config (10 stars, last pushed 21d ago), licensed MIT. It adds 4,290 tokens to every session, about $0.0215 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-09-07.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens