Agent Atlas

Plate II

The Scaffold

Before an agent reads your request, it has already read a stack of files you may never have opened. Pick a harness and a task, and see which files it loads, which it saves for later, and which it never sees at all.

Harness
Task
Experiments

The files

What Claude Code does with each one. Select a file to open its drawer.

In your home folder

In the project

  • Project instructions for any agent Factual

    Claude Code
    Loaded into the context when the session starts, every time.
    Codex
    Loaded into the context when the session starts, every time.
    Shared with your team
    Yes, committed to Git.

    What it is for

    The map of the project: how to build and test it, rules that are easy to break, and where the deeper documents live. Shared by every agent and every teammate.

    A small example

    # My app
    - Run `npm test` before you call anything done.
    - Never edit files in `generated/`.
    - Architecture: docs/architecture.md

    Common mistakes

    • Writing an encyclopedia. Every line is paid for on every turn of every session.
    • Restating what the code already shows.
    • Rules that a script could check instead.

    How we know: Codex: AGENTS.md documentation. Claude Code: tested in fresh headless sessions of 2.1.319 on 2026-11-08 with codeword files. With no CLAUDE.md, AGENTS.md loaded at the start. With a CLAUDE.md beside it and no import line, AGENTS.md was ignored.

What happens

About 1,005 tokens load before you type a word, and they are read again on every turn. Simplified

  1. StartLoads ~/.claude/CLAUDE.md · ~150 tokens
  2. StartLoads AGENTS.md · ~300 tokens
  3. StartLoads CLAUDE.md · ~10 tokens
  4. StartLists the release skill (description only) · ~25 tokens
  5. StartLoads ~/.claude/projects/<repo>/memory/MEMORY.md · ~120 tokens
  6. StartLoads .mcp.json · ~400 tokens
  7. DuringWorks in src/. With a CLAUDE.md at the root, src/AGENTS.md did not load on its own in our test. Point to it from the root file
  8. ThenYour request: “Fix a bug in src/app.ts.”

Three ideas to take away

Instruction files are a map, not a manual. Whatever loads at the start is paid for on every turn. Keep it short and point to the deeper documents.

Text asks, code enforces. A rule in AGENTS.md is advice the model usually follows. A rule in settings or a hook is applied by the harness whether the model agrees or not.

One fact, one home. If the same rule lives in two files, they will eventually disagree. Import or link instead of copying.