Guide · from the data

How AGENTS.md files talk about your tools: what projects tell coding agents, tool by tool

What open-source projects tell their coding agents about Playwright, pnpm, TypeScript, Docker and 64 more tools — the recurring instructions, in our words, each with the files that say it.

Published
October 12, 2026
Numbers refreshed
October 12, 2026
Reading time
20 min
Share
Post on X

An instruction file is where a project tells its coding agent the things it would otherwise get wrong: which test runner, which package manager, what never to touch. We read the lines that name a tool in the AGENTS.md and CLAUDE.md files of open-source products' repos, and grouped what they say. Below are the 229 things at least three files tell their agents about the same tool, across 68 tools and 449 repos.

Each note is in our words. The number is how many files say it; open a note for the repos.

TypeScriptProgramming Language · named in 288 files

npmRuntime & Build Tools · named in 228 files

ReactFrontend Framework · named in 207 files

PythonProgramming Language · named in 178 files

pnpmMonorepo · named in 176 files

Claude CodeAI Coding Assistants · named in 164 files

DockerServers & Self-Hosting · named in 143 files

ViteRuntime & Build Tools · named in 118 files

pytestTesting · named in 116 files

VitestTesting · named in 115 files

PlaywrightBrowser Automation for Agents · named in 110 files

Node.jsProgramming Language · named in 100 files

ESLintLinting & Formatting · named in 97 files

Next.jsFrontend Framework · named in 93 files

PostgreSQLDatabase · named in 82 files

CursorAI Coding Assistants · named in 75 files

SQLiteDatabase · named in 74 files

BunMonorepo · named in 67 files

PrettierLinting & Formatting · named in 67 files

RedisCaching & Key-Value · named in 64 files

RustProgramming Language · named in 60 files

FastAPIBackend Framework · named in 58 files

GitHub ActionsCI/CD · named in 55 files

Tailwind CSSStyling · named in 55 files

ElectronDesktop Framework · named in 48 files

ZodData Validation · named in 46 files

BiomeLinting & Formatting · named in 40 files

CloudflareHosting · named in 35 files

JestTesting · named in 34 files

PydanticData Validation · named in 33 files

GraphQLAPI Layer & Data Fetching · named in 32 files

TurborepoMonorepo · named in 31 files

VercelHosting · named in 31 files

ZustandState Management · named in 29 files

RuffLinting & Formatting · named in 28 files

shadcn/uiUI Components · named in 28 files

YarnRuntime & Build Tools · named in 27 files

DiscordCommunity · named in 26 files

ChangesetsMonorepo · named in 25 files

MDXMarkdown & Code Rendering · named in 25 files

ExpressBackend Framework · named in 24 files

SentryError Monitoring · named in 24 files

SlackCommunity · named in 24 files

OpenTelemetryLogs & Traces · named in 21 files

StorybookTesting · named in 21 files

SupabaseDatabase · named in 21 files

Drizzle ORMDatabase Access & ORMs · named in 20 files

SQLAlchemyDatabase Access & ORMs · named in 20 files

TauriDesktop Framework · named in 20 files

ExpoApp Store Release · named in 19 files

KubernetesServers & Self-Hosting · named in 19 files

React NativeMobile Framework · named in 19 files

TanStack QueryAPI Layer & Data Fetching · named in 19 files

MySQLDatabase · named in 18 files

OllamaRun Models Locally · named in 18 files

VS CodeCode Editor & Terminal · named in 18 files

i18nextInternationalization · named in 17 files

PrismaDatabase Access & ORMs · named in 17 files

SvelteFrontend Framework · named in 17 files

GitHub CopilotAI Coding Assistants · named in 16 files

MongoDBDatabase · named in 16 files

React RouterFrontend Framework · named in 16 files

webpackRuntime & Build Tools · named in 16 files

AstroFrontend Framework · named in 15 files

HonoBackend Framework · named in 15 files

OpenAI CodexAI Coding Assistants · named in 15 files

PHPProgramming Language · named in 15 files

StripePayments · named in 15 files

How we counted

From each repo's AGENTS.md (or its CLAUDE.md, when that isn't just a pointer to AGENTS.md), we took up to three lines naming the tool outside code blocks, for up to 150 files per tool. One reader grouped each tool's lines into notes; a second checked every cited repo against its lines and dropped the ones that didn't say it. A note shared by fewer than three files is left out, so the counts are a floor: a file can say the same thing in a line we didn't read. Tools whose names are also ordinary words are left out. The files are their authors' writing, so nothing here quotes them.