How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
shadowsocksAGENTS.mdshadowsocks/ShadowsocksX-NG/ShadowsocksX-NG2/AGENTS.md
root [`AGENTS.md`](../AGENTS.md) for repository conventions and [`README.md`](README.md) for project and development documentation. ## Testing principles - Keep unit tests hostless and access packaged resources through explicit dependency injection. - Isolate test
SigNozAGENTS.mdSigNoz/signoz/frontend/AGENTS.md
testid or testId (if supported) to critical/behavioral components like inputs, buttons, etc... - When creating test, these IDs should be used instead of finding by role. - Never create barrel files. - When
refined-githubAGENTS.mdrefined-github/refined-github/agents.md
enhances the actual GitHub website. A change that looks correct, builds, or passes automated tests is not sufficient. It must be demonstrated to work on the real GitHub website with
filamentphpAGENTS.mdfilamentphp/filament/AGENTS.md
doing its work. If your agent cannot load skills, read the linked `SKILL.md` directly. - **Testing**: Load [testing-filament](.agents/skills/testing-filament/SKILL.md) when planning verification, adding or changing tests, running tests, or validating
No other project uses it yet
conductor-ossAGENTS.mdconductor-oss/conductor/AGENTS.md
build system. ## Setup Commands | Command | Description | |---------|-------------| | `./gradlew build` | Build the entire project | | `./gradlew test` | Run all tests | | `./gradlew :module-name:test` | Run tests for a specific module | | `./gradlew spotlessApply` | Apply
atuinshAGENTS.mdatuinsh/atuin/AGENTS.md
nursery` on main crate. CI enforces `-D warnings`, on both the default targets and `--tests`. - Rustdoc: CI runs `cargo doc --document-private-items --no-deps --workspace` with `RUSTDOCFLAGS=-D warnings
Steady12 mentions in 2 weeks
No other project uses it yet
hasuraAGENTS.mdhasura/graphql-engine/AGENTS.md
intact. ## Building and typechecking For any haskell code changes use `cabal build all --enable-tests --enable-benchmarks` to check your work and iterate until it builds cleanly. Make sure
Steady6 mentions in 2 weeks
No other project uses it yet
yetoneAGENTS.mdyetone/magpie/AGENTS.md
plugin paths in `internal/gui/assets/app.js`: `subOf`, `pluginSubs` and `startPluginSignIn`. The parity tests, `internal/gateway/plugin_*_test.go`, hold each plugin to what its built
No other project uses it yet
OpenAIAGENTS.mdopenai/openai-python/AGENTS.md
follow [Modifying/Adding code](CONTRIBUTING.md#modifyingadding-code) to identify schema/generator/handwritten ownership. Keep handwritten policy, automation, tests, and examples small; alter exported APIs only when explicitly required. ## Security requirements for coding agents
Steady5 mentions in 2 weeks
No other project uses it yet
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.
