agentsmd/agents.md
#301 this week
AGENTS.md — a simple, open format for guiding coding agents
24.2K stars
1.8K forks
24.2K GitHub watchers
Updated 9/8/2026
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Use Cases & Benefits
- Defines a simple, open format called AGENTS.md for providing context and instructions to AI coding agents within a project.
- Offers a standardized, predictable place to guide AI agents, improving their effectiveness and integration in development workflows.
- Use for documenting environment setup and tooling tips to help AI agents understand project-specific commands and dependencies.
- Use for specifying testing and CI instructions to enable AI agents to run and validate tests accurately before code merges.
- Use for outlining pull request conventions and code quality checks to assist AI agents in maintaining consistent contribution standards.
About agents.md
AGENTS.md
AGENTS.md is a simple, open format for guiding coding agents.
Think of AGENTS.md as a README for agents: a dedicated, predictable place to provide context and instructions to help AI coding agents work on your project.
Below is a minimal example of an AGENTS.md file:
# Sample AGENTS.md file
## Dev environment tips
- Use `pnpm dlx turbo run where <project_name>` to jump to a package instead of scanning with `ls`.
- Run `pnpm install --filter <project_name>` to add the package to your workspace so Vite, ESLint, and TypeScript can see it.
- Use `pnpm create vite@latest <project_name> -- --template react-ts` to spin up a new React + Vite package with TypeScript checks ready.
- Check the name field inside each package's package.json to confirm the right name—skip the top-level one.
## Testing instructions
- Find the CI plan in the .github/workflows folder.
- Run `pnpm turbo run test --filter <project_name>` to run every check defined for that package.
- From the package root you can just call `pnpm test`. The commit should pass all tests before you merge.
- To focus on one step, add the Vitest pattern: `pnpm vitest run -t "<test name>"`.
- Fix any test or type errors until the whole suite is green.
- After moving files or changing imports, run `pnpm lint --filter <project_name>` to be sure ESLint and TypeScript rules still pass.
- Add or update tests for the code you change, even if nobody asked.
## PR instructions
- Title format: [<project_name>] <Title>
- Always run `pnpm lint` and `pnpm test` before committing.
Website
This repository also includes a basic Next.js website hosted at https://agents.md/ that explains the project’s goals in a simple way, and featuring some examples.
Running the app locally
- Install dependencies:
pnpm install - Start the development server:
pnpm run dev - Open your browser and go to http://localhost:3000
Discover Repositories
Search across tracked repositories by name or description