← All notes

What developers put in agent context files

Short answer

Mostly build and test commands, implementation notes and architecture; rarely security or performance. The files grow like config code through many small edits. [S1][S2]

Numbers (as reported)

A study of 2,303 files found tests 75.9%, implementation details 70.8%, architecture 68.1%, security 14.8%, performance 14.5%. [S1] A study of 253 manifests found shallow structure: one main heading and a few subsections. [S2]

Takeaway

Add explicit security and performance guardrails if they matter.

Claims

Sources

License: this note is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Summary by iinventedlight (AI-assisted).

License: CC-BY-4.0 · Summary by iinventedlight (AI-assisted). Sources: arXiv, [2511.12884] Agent READMEs: An Empirical Study of Context Files for Agentic Coding, CC BY 4.0; arXiv, [2509.14744] On the Use of Agentic Coding Manifests: An Empirical Study of Claude Code, CC BY 4.0.

Cite this

Permanent ID: iil:note:6rjn57mz

iinventedlight. 2026. "What developers put in agent context files." iinventedlight Library, iil:note:6rjn57mz, version of 2026-11-04. https://iinventedlight.com/library/notes/ao-rules-context-files-in-practice/. License: CC-BY-4.0.

@misc{iil_note_6rjn57mz,
  author = {{iinventedlight}},
  title = {{What developers put in agent context files}},
  howpublished = {iinventedlight Library},
  year = {2026},
  date = {2026-11-04},
  url = {https://iinventedlight.com/library/notes/ao-rules-context-files-in-practice/},
  note = {Permanent ID iil:note:6rjn57mz. License: CC-BY-4.0.},
}

Markdown

Spotted a mistake? Use the MCP feedback tool or email hello@iinventedlight.com.

For language models and agents: start at /llms.txt. This page in Markdown: /library/notes/ao-rules-context-files-in-practice.md.