# AGENTS.md, CLAUDE.md, SKILL.md and Cursor rules: which file does what

By markdownregistry. Published October 2, 2026. Updated October 2, 2026.

AGENTS.md and CLAUDE.md hold a project's standing instructions; SKILL.md defines one skill an agent loads only when a task needs it; Cursor rules are Cursor's own instruction files; DESIGN.md describes a design system; and llms.txt maps a website's documentation for AI models. Which agent reads which file is set by each agent's documentation, so every claim below links the page it comes from. The counts come from the registry's own crawl of public GitHub, [State of agent markdown, September 2026](https://markdownregistry.com/reports/state-of-agent-markdown-2026-09).

| Kind | Files | Graded A | Share graded A |
| --- | --- | --- | --- |
| SKILL.md | 61,170 | 57,008 | 93.2% |
| AGENTS.md | 3,901 | 3,570 | 91.5% |
| CLAUDE.md | 2,081 | 1,387 | 66.7% |
| DESIGN.md | 1,042 | 1,025 | 98.4% |
| Cursor rules | 510 | 460 | 90.2% |
| llms.txt | 415 | 351 | 84.6% |

Agent markdown files in the registry by kind, and the share whose latest version passes every automatic check (grade A). Registry crawl, data frozen September 27, 2026; method and downloads in [the report](https://markdownregistry.com/reports/state-of-agent-markdown-2026-09).

Every claim about another tool was checked against that tool's own documentation on October 2, 2026. Figures are from [State of agent markdown, September 2026](https://markdownregistry.com/reports/state-of-agent-markdown-2026-09), data frozen September 27, 2026.

## SKILL.md vs AGENTS.md vs CLAUDE.md: which file does what?

AGENTS.md and CLAUDE.md do the same job: they hold a project's standing instructions, what an agent should know before it changes any code, such as how to build and test and which conventions to follow. AGENTS.md is the shared name that many coding agents read, including Codex, Cursor and GitHub Copilot; CLAUDE.md is Claude Code's own file. SKILL.md is different: it defines one skill, a folder of instructions and optional scripts that an agent reads only when a task calls for it, so an agent can carry many skills without filling its context.

| File | What it is for | Where it lives | Who reads it |
| --- | --- | --- | --- |
| `AGENTS.md` | A project's standing instructions for coding agents: build and test commands, conventions, warnings | The repository root, plus one inside any package that needs its own | Codex, Cursor, GitHub Copilot's agents and many others (agents.md lists them); Claude Code when there is no CLAUDE.md |
| `CLAUDE.md` | The same job, for Claude Code | `./CLAUDE.md` or `./.claude/CLAUDE.md`, `~/.claude/CLAUDE.md` for you alone, and subfolders | Claude Code. GitHub Copilot also accepts one at the repository root |
| `SKILL.md` | One skill: a name and a description in frontmatter, then instructions, beside optional scripts and reference files | Its own folder, for Claude Code `.claude/skills/<name>/SKILL.md` | Agents that support the Agent Skills format, loaded only when a task calls for it |
| Cursor rules | Cursor's project instructions, applied to every chat, to matching files, when relevant, or when mentioned | `.mdc` files in `.cursor/rules` | Cursor |
| `DESIGN.md` | A design system: exact tokens in YAML front matter, the reasons in prose | The repository root | An agent that is pointed at it |
| `llms.txt` | A map of a website's documentation for AI models, as markdown links | `/llms.txt` on a website | Any model or agent that fetches it |

## AGENTS.md vs CLAUDE.md: what is the difference, and do I need both?

The difference is who reads them. AGENTS.md is an open format, now stewarded by the Agentic AI Foundation under the Linux Foundation, that many coding agents read; CLAUDE.md is the file Claude Code reads. You need only one of them if every agent your team uses reads it. If you use Claude Code alongside other agents, write the instructions once in AGENTS.md: Claude Code reads AGENTS.md when the project has no CLAUDE.md, and if you want a CLAUDE.md as well, give it the line @AGENTS.md so it imports the shared file instead of repeating it.

Claude Code reads a CLAUDE.md in place of AGENTS.md when both exist, and its docs list a few places where the two still behave differently, such as `InstructionsLoaded` hooks, which fire for CLAUDE.md and not for an AGENTS.md read on its own ([Claude Code: where AGENTS.md differs](https://code.claude.com/docs/en/memory#where-agents-md-differs-from-claude-md)). In the registry's crawl there are 3,901 AGENTS.md files and 2,081 CLAUDE.md files.

## Does Claude Code read AGENTS.md if there is no CLAUDE.md file?

Yes, from Claude Code version 2.1.277. By default it reads AGENTS.md only when there is no CLAUDE.md, .claude/CLAUDE.md or CLAUDE.local.md in your working directory or any directory above it; when there is one, it reads the CLAUDE.md files instead. Your personal ~/.claude/CLAUDE.md does not count for that check. To have it read both, set Project instructions to claude-md-and-agents-md in /config. Older versions, and some sessions before version 2.1.281 such as those on Amazon Bedrock or with telemetry disabled, read CLAUDE.md only, so in those sessions give Claude Code your AGENTS.md through a CLAUDE.md that contains the line @AGENTS.md.

| Instruction files in your repository | What Claude Code reads by default |
| --- | --- |
| AGENTS.md, and no CLAUDE.md or CLAUDE.local.md in the working directory or above it | AGENTS.md |
| AGENTS.md, and a CLAUDE.md or CLAUDE.local.md in the working directory or above it | The CLAUDE.md files only |
| A CLAUDE.md that imports AGENTS.md | CLAUDE.md, with AGENTS.md included through the import |

It does not read `AGENTS.local.md`, `AGENTS.override.md` or anything under `.agents/`. A `CLAUDE.local.md` counts as a CLAUDE.md here, so adding one for your own notes stops Claude Code reading AGENTS.md unless you choose `claude-md-and-agents-md`. Source: [Claude Code docs, AGENTS.md](https://code.claude.com/docs/en/memory#agents-md).

## How do I keep AGENTS.md and CLAUDE.md in sync in the same repo?

Keep the instructions in one file and point the other at it. Write them in AGENTS.md, and make CLAUDE.md a file whose first line is @AGENTS.md, an import Claude Code expands, with any Claude-only instructions below it. A symlink made with ln -s AGENTS.md CLAUDE.md also works, but Claude Code's docs advise the import if anyone clones the repository on Windows, where a committed symlink can check out as a one-line text file. Two copies of the same text drift apart; an import cannot.

```
@AGENTS.md

## Claude Code

Use plan mode for changes under `src/billing/`.
```

That is the example from [Claude Code's docs](https://code.claude.com/docs/en/memory#share-one-file-with-other-coding-tools). Run `/context` in the next session and check that CLAUDE.md appears under Memory files. Of 1,203 folders in the registry's crawl of public GitHub that hold both files, 347 (28.8%) use this import and 426 (35.4%) keep two separate files; [our count of what those folders do](https://markdownregistry.com/blog/agents-md-and-claude-md-in-one-repo) has the rest. These files change often: in the registry's crawl, at least 27.8% (730 of the 2,623 first indexed at least 14 days before the data was frozen) got an upstream commit dated within 14 days after first indexing for AGENTS.md, and for CLAUDE.md at least 23.2% (309 of the 1,333 first indexed at least 14 days before the data was frozen) got an upstream commit dated within 14 days after first indexing, each a lower bound.

## Cursor rules vs AGENTS.md: which one should I use for my repo?

Use AGENTS.md when plain instructions are enough or when more than one agent works in the repository: Cursor reads AGENTS.md in the project root and in subdirectories, and so do many other agents. Use Cursor rules, .mdc files in .cursor/rules, when you need what only they do: a rule applied only when matching files are in context, one the agent pulls in when its description is relevant, or one used only when you mention it. Cursor ignores a plain .md file in .cursor/rules, because the rule's frontmatter is what tells Cursor when to apply it.

A rule's frontmatter decides when it applies: `alwaysApply: true` for every chat, `globs` for matching files, a `description` for the agent to judge, or none of them for an @-mention only ([Cursor docs, Rules](https://cursor.com/docs/rules)). The registry indexes 510 Cursor rules files, both `.cursor/rules/*.mdc` and `.cursorrules`; browse them at [Cursor rules](https://markdownregistry.com/kind/rules). Which rule types projects actually use, and the setting that makes Cursor ignore a rule's file pattern, are counted in [how projects write Cursor rules](https://markdownregistry.com/blog/how-projects-write-cursor-rules).

## What is a CLAUDE.md file in Claude Code?

A CLAUDE.md file is a markdown file of standing instructions that Claude Code reads at the start of every session: build and test commands, conventions, project layout, and rules that hold in every session. A project's file lives at ./CLAUDE.md or ./.claude/CLAUDE.md and is committed for the whole team; ~/.claude/CLAUDE.md holds your own instructions for every project, and CLAUDE.local.md your own for one project. A CLAUDE.md in a subfolder loads when Claude Code reads files in that folder. Run /init to generate a first version from your codebase.

To start one, [this CLAUDE.md template](https://mdpantry.com/s/st_ayte7u4rzrr4puyh) marks what to change for your project. Claude Code's docs suggest adding to it when Claude makes the same mistake twice or when you retype the same correction, and moving multi-step procedures into a skill instead ([Claude Code docs, memory](https://code.claude.com/docs/en/memory)). Real examples: [2,081 CLAUDE.md files from public GitHub](https://markdownregistry.com/kind/claude), most-starred repositories first.

## How to write a good AGENTS.md file for my repository

Put AGENTS.md at the repository root and write what a new teammate would need before changing code: a project overview, the exact build and test commands, code style, testing instructions and security notes, the sections agents.md suggests. Keep it to facts that hold for every task, and keep it short: Codex stops adding project instructions once they reach 32 KiB combined, by default. In a monorepo, put another AGENTS.md inside each package that needs one; agents read the nearest file, so the closest one wins.

Agents run the commands you list, so write them exactly as they should be typed. To start from a file with each section explained, use [this AGENTS.md template](https://mdpantry.com/s/st_zdlp6lbqoiyo3ecb), which says what to change in it. In Codex, an `AGENTS.override.md` in a directory replaces that directory's AGENTS.md ([Codex docs](https://developers.openai.com/codex/guides/agents-md)). To read what others wrote, the registry lists [3,901 AGENTS.md files](https://markdownregistry.com/kind/agents) from public GitHub, most-starred repositories first, each with its version history.

## What is DESIGN.md and how do AI coding agents use it?

DESIGN.md is a markdown file that describes a project's visual design system so coding agents build interfaces that match it. The format published by Google Labs puts exact design tokens, such as colors, type and spacing, in YAML front matter and explains in prose why they exist and how to apply them; its own repository marks it as an alpha version. An agent uses it as it uses any instruction file, by reading it. None of the agent docs linked on this page says it loads DESIGN.md on its own, so point to it from a file your agent does load, for example an @DESIGN.md line in CLAUDE.md, which Claude Code expands.

The format's repository ships a linter: `npx @google/design.md lint DESIGN.md` ([google-labs-code/design.md](https://github.com/google-labs-code/design.md)). The registry indexes 1,042 DESIGN.md files with every version it has recorded, at [DESIGN.md files](https://markdownregistry.com/kind/design). Many are templates: 53.3% (555) are at least 200 bytes and byte-identical to a file in another repository, and 540 of those copies sit in the four repositories holding the most.

How the files in the registry fare against that linter is counted in [DESIGN.md files against the official linter](https://markdownregistry.com/blog/design-md-files-against-the-official-linter): most hold no tokens at all.

## How to add an llms.txt file to my website

Publish a markdown file at /llms.txt on your site. The llms.txt proposal asks for an H1 with the site or project name, which is the only required part, then a blockquote with a short summary, optional paragraphs, and sections under H2 headings that list links to the pages a model should read, each written [name](url) with an optional note after a colon. A file can also sit at a subpath such as /docs/llms.txt and cover the pages under it. The proposal also suggests serving a clean markdown copy of each page at the same URL with .md added.

```
# Project name

> One or two sentences on what the project is.

## Docs

- [Quick start](https://example.com/start.md): install and first run

## Optional

- [Changelog](https://example.com/changelog.md)
```

The Optional section is, by convention, for links an agent can skip when it needs a shorter context ([llmstxt.org](https://llmstxt.org/)).

How closely real files follow this shape is counted in [how llms.txt files follow the format](https://markdownregistry.com/blog/how-llms-txt-files-follow-the-format): most get the H1 and summary right, and fewer keep their H2 sections as lists of links.

## Where can I find llms.txt examples from real websites?

The llms.txt proposal points to three from the AI labs' own developer docs: OpenAI at developers.openai.com/llms.txt, Anthropic at docs.anthropic.com/llms.txt (which now redirects, through platform.claude.com/docs/llms.txt, to platform.claude.com/llms.txt) and Google's Gemini at ai.google.dev/gemini-api/docs/llms.txt. For more, the registry indexes llms.txt and llms-full.txt files committed to public GitHub repositories, with each version it has recorded; a file in a repository may differ from what a website serves.

Open the three: [OpenAI](https://developers.openai.com/llms.txt), [Anthropic](https://platform.claude.com/llms.txt), [Gemini](https://ai.google.dev/gemini-api/docs/llms.txt). The registry's [415 llms.txt files](https://markdownregistry.com/kind/llmstxt) change faster than any other kind it tracks: at least 41.2% (106 of the 257 first indexed at least 14 days before the data was frozen) got an upstream commit dated within 14 days after first indexing, a lower bound.

## Where can I search real CLAUDE.md files from popular GitHub repos?

markdownregistry indexes CLAUDE.md files from public GitHub repositories, along with AGENTS.md, SKILL.md, Cursor rules, DESIGN.md and llms.txt files, and lists each kind with the most-starred repositories first. Every file keeps each version the registry has recorded, with a diff between versions and an audit grade, and the search page covers all of them. When its report was frozen on September 27, 2026, it held 2,081 CLAUDE.md files, 3,901 AGENTS.md files, 510 Cursor rules, 1,042 DESIGN.md files and 415 llms.txt files.

Browse by kind: [CLAUDE.md](https://markdownregistry.com/kind/claude) · [AGENTS.md](https://markdownregistry.com/kind/agents) · [SKILL.md](https://markdownregistry.com/kind/skill) (61,170) · [Cursor rules](https://markdownregistry.com/kind/rules) · [DESIGN.md](https://markdownregistry.com/kind/design) · [llms.txt](https://markdownregistry.com/kind/llmstxt), or [search all of them](https://markdownregistry.com/search). The registry finds repositories through GitHub topic and README searches, so this is its crawl, not every file on GitHub.

## Sources

- [Claude Code docs: CLAUDE.md, AGENTS.md and imports](https://code.claude.com/docs/en/memory)
- [AGENTS.md](https://agents.md/)
- [Cursor docs: Rules](https://cursor.com/docs/rules)
- [Codex docs: AGENTS.md](https://developers.openai.com/codex/guides/agents-md)
- [GitHub docs: repository custom instructions for Copilot](https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions)
- [google-labs-code/design.md](https://github.com/google-labs-code/design.md)
- [llmstxt.org: the llms.txt proposal](https://llmstxt.org/)
- [Agent Skills specification](https://agentskills.io/specification)

Last checked October 2, 2026. The page: https://markdownregistry.com/guides/agents-md-vs-claude-md