n8n
n8n-io/n8n/AGENTS.md
Essential Commands For routine pre-commit checks, follow [Verify changes](#verify-changes). For focused tests, use `pnpm agent:test` or `pnpm agent:playwright`. Pass test files and worker limits after
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.
n8n-io/n8n/AGENTS.md
Essential Commands For routine pre-commit checks, follow [Verify changes](#verify-changes). For focused tests, use `pnpm agent:test` or `pnpm agent:playwright`. Pass test files and worker limits after
firecrawl/firecrawl/AGENTS.md
here are the general steps you should take: 1. Write some end-to-end tests that assert your win conditions, if they don't already exist - 1 happy path (more
Steady20 mentions in 2 weeks
No other project uses it yet
instructkr/claude-code/AGENTS.md
Cargo workspace: 11 crates, `claw` binary ├── src/ # Python porting workspace + reference_data/ parity snapshots ├── tests/ # Python unittest validation of src/ + scripts/ (stdlib unittest) ├── docs/ # g0XX gate verification maps + topic docs
3 projects use a version of this
instructkr/claude-code/rust/AGENTS.md
Anthropic Messages API. Prints `MOCK_ANTHROPIC_BASE_URL`. Dev-dep for CLI and analog tests. | | `runtime` | lib | Core: sessions, permissions, MCP, conversation loop. ~47 modules. | | `api` | lib | Provider clients: Anthropic
3 projects use a version of this
instructkr/claude-code/src/AGENTS.md
Real logic (permissions, path scoping) | `permissions.py`, `path_scope.py` | | Query engine shim | `query_engine.py` | | Runtime simulation | `runtime.py` | | Tests | repo-root `tests/` (test_porting_workspace.py, test_security_scope.py) | Run tests: `python -m unittest discover -s tests` from repo
3 projects use a version of this
microsoft/vscode/extensions/copilot/src/extension/chatSessions/copilotcli/AGENTS.md
copilotCLIPrompt.ts # Prompt reference extraction and parsing │ ├── customSessionTitleService.ts │ ├── delegationSummaryService.ts │ ├── utils.ts # SessionIdForCLI namespace (URI scheme: 'copilotcli') │ └── test/ │ ├── node/ # Node.js-specific (SDK integration, filesystem, permissions) │ ├── copilotCli.ts # ICopilotCLISDK, CopilotCLIModels, CopilotCLIAgents │ ├── copilotcliSession.ts # CopilotCLISession — main session
microsoft/vscode/src/vs/platform/agentHost/AGENTS.md
# Multi-Chat Architecture > Node runtime service construction is documented separately in [`node/serviceBootstrapping.md`](node/serviceBootstrapping.md). Host
microsoft/vscode/src/vs/platform/agentHost/node/copilot/prompts/AGENTS.md
overridden sections) and the full config at `trace`. Keep new config shapes summarizable there. - **Tests.** `../../../test/node/agentHostPromptRegistry.test.ts` covers the registry/wiring; `../../../test/node/toolInstructions.test.ts` covers the composition/gating. Add cases there, not new harnesses
microsoft/vscode/src/vs/platform/agentHost/test/node/AGENTS.md
Agent host unit tests For tests in this area that touch the SessionDatabase, they MUST use an in-memory database, not a real database file on disk. Use `SessionDatabase.open(':memory
avelino/awesome-go/AGENTS.md
generator. - `.github/workflows/`: CI pipelines for PR quality validation, stale checks, site deployment, and Go tests. ## When Modifying the Awesome List - Read and respect `CONTRIBUTING.md` (alphabetical order, one item
Significant-Gravitas/AutoGPT/AGENTS.md
Styling**: Tailwind CSS only, use design tokens, Hugeicons only (through the `Icon` atom) 5. **Testing**: Integration tests (Vitest + RTL + MSW) are the default (~90%, page-level). Playwright for E2E critical
Steady3 mentions in 2 weeks
No other project uses it yet
Significant-Gravitas/AutoGPT/autogpt_platform/AGENTS.md
files, and the `check-env-defaults-blank` pre-commit hook (plus the matching unit test in `single-container/tests/test_runtime_config.py`, which CI runs) asserts that the settings listed in `BLANK
DietrichGebert/ponytail/AGENTS.md
task and the code it touches. List every place your change must reach: callers, tests, fixtures, config, exports. Check what your change could break for users: data it would destroy
Steady11 mentions in 2 weeks
No other project uses it yet
f/awesome-chatgpt-prompts/AGENTS.md
AUTH_AZURE_AD_ISSUER= ``` Optional features: ``` OPENAI_API_KEY= # For AI-powered semantic search ``` ## Testing Currently no automated tests. When implementing: - Place tests adjacent to source files or in `__tests
2 projects use a version of this
twbs/bootstrap/AGENTS.md
lint` / `npm run js-lint` — lint - `npm run docs-build` — build docs site - `npm test` — full test suite (lint + dist + tests + docs) ## Writing style Use ASD-STE100 Simplified Technical English
No other project uses it yet
huggingface/transformers/.ai/AGENTS.md
docstrings. - `make check-repo` — `make typing` plus consistency checks. - `RUN_SLOW=1 pytest ...` — many tests are marked slow and skipped in CI. Run `make style` (or `make fix-repo
No other project uses it yet
langgenius/dify/AGENTS.md
docs/BACKEND_DATABASE_SCHEMA.md) guides. ## Repository Gotchas - Run backend commands through `uv run --project api `. - Backend integration tests are CI-only and are not expected to run locally. - Keep `docker/.env.example` limited to variables
langgenius/dify/api/AGENTS.md
repository root: - Format and lint: `make lint` - Type check: `make type-check` - Unit tests: `make test` - Targeted tests: `make test TARGET_TESTS=./api/tests/ ` Run direct Python commands through
langgenius/dify/cli/AGENTS.md
requires the Bun version pinned in `.bun-version`; command-tree generation and the `dev`, `test`, and `build` pre-scripts invoke it. Read [`ARD.md`] before adding a command or changing shared
No other project uses it yet
langgenius/dify/dify-agent/AGENTS.md
agent/`: - Lint: `make check` - Format and fix lint: `make fix` - Type check: `make typecheck` - Tests: `make test` Use the package's `uv` environment and Pydantic v2 APIs. Inspect current dependency
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.