AGENTS.md is the emerging convention for telling a coding agent how to work in a repository. PolicyCodex compiles your enforced corpus into that format, so you write standards once and every agent that reads the file picks them up.

​
Getting the file

RFCs → Export AGENTS.md downloads the compiled file for your organisation.

​
What it contains

Only enforced statements — the rules that currently block. Sectioned by domain, MUST before SHOULD, with each statement’s slug carried as an anchor comment so a finding can be traced back to the governed statement it came from. Advisory (approved) standards are deliberately excluded. A file an agent treats as absolute should only contain rules you are prepared to block on.

​
Keeping it fresh

A committed AGENTS.md is a snapshot. Approve a new RFC and the file in the repository is immediately out of date.

Prefer MCP

Where the agent supports it, the MCP server is always current. No refresh step, no drift.

Regenerate in CI

Where a file is the only option, fetch it from /v1/compile/agents-md on a schedule and open a pull request when it changes.
A scheduled refresh, roughly:
Follow it with your usual “open a PR if the working tree changed” step, so the update goes through review like any other change.

​
Scope per repository

Compile the domains that repository actually needs:
Shipping the entire corpus to every repository buries the relevant rules in irrelevant ones, and agents respond to that the same way people do.

​
Other agent formats

.cursor/rules and copilot-instructions compile targets exist as stubs and are not production-ready. Use AGENTS.md or MCP today.
Agent neutrality is the point: PolicyCodex rides the AGENTS.md convention rather than competing with it, so the corpus is not locked to one vendor’s agent.