AGENTS.md — Cross-Tool AI Agent Entry Point
By Amr
How the repository-root AGENTS.md file provides a single source of truth for AI coding agents (Copilot, Codex, Cursor, Aider, Jules, Continue, Claude Code, and others).
Estimated reading time: 2 minutes
Table of Contents
AGENTS.md — Cross-Tool AI Agent Entry Point
AGENTS.md in the repository root is a single, short entry-point file for AI coding agents. It follows the emerging agents.md convention and is read by GitHub Copilot, OpenAI Codex, Cursor, Aider, Jules, Continue, Claude Code, and any other agent that respects the convention.
Why AGENTS.md?
Different AI tools each have their own config file format:
| Tool | Its own file |
|---|---|
| GitHub Copilot | .github/copilot-instructions.md |
| Cursor | .cursor/ rules |
| Aider | .aider.conf.yml |
| Continue | .continuerc.json |
Rather than maintaining separate instruction files with duplicated content, AGENTS.md acts as a cross-tool entry point that links to the canonical, detailed guidance already in .github/. This prevents drift and keeps a single source of truth.
File Location
AGENTS.md ← repository root
GitHub Copilot also reads it as supplementary context. Other tools that support the AGENTS.md convention will discover it automatically.
What It Contains
AGENTS.md is intentionally short. It covers:
- Project snapshot — what the repo is, primary languages, version source of truth
- Guidance map — a table showing which file to read for which task
- Essential commands — the handful of commands every agent needs
- Operating rules — seven concise rules (minimal changes, validate before done, etc.)
- Extension guide — how to add new agent capabilities
Layered Guidance Model
AGENTS.md ← Cross-tool entry point (always read first)
│
├── .github/copilot-instructions.md ← Full architecture & conventions
│
└── .github/instructions/*.instructions.md ← File-scoped rules
layouts.instructions.md → _layouts/**
includes.instructions.md → _includes/**
scripts.instructions.md → scripts/**
sass.instructions.md → _sass/**, assets/css/**
obsidian.instructions.md → _plugins/obsidian_links.rb, …
testing.instructions.md → test/**
documentation.instructions.md → docs/**, pages/_docs/**
version-control.instructions.md → CHANGELOG.md, version.*, …
features.instructions.md → features/features.yml, _data/features.yml
install.instructions.md → install.sh, scripts/lib/install/**, …
Operating Rules for Agents
All agents working in this repository must follow these rules (quoted from AGENTS.md):
- Make minimal, surgical changes. Match the existing style. Do not refactor unrelated code.
- Respect the layered guidance. File-scoped instructions override generic best practices.
- Validate before declaring done. Run relevant tests; for theme changes run the Docker Jekyll build.
- Update
CHANGELOG.mdfor any user-visible change. - Bump the version only via
./scripts/bin/release— never in unrelated PRs. - Do not commit secrets. Use environment variables.
- Prefer existing libraries and patterns.
Adding a New Tool
To onboard a new AI tool without duplicating content:
- Create the tool’s own config file (e.g.
CLAUDE.md) - In that file, write: “See
AGENTS.md.” - That’s it — the layered guidance already covers everything
Related
See also
- [[Development]]
- [[Documentation]]