AGENTS.md examples from real projects

instructkrAGENTS.md

claude-code / rust

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

instructkrAGENTS.md

claude-code / src

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

MicrosoftAGENTS.md

vscode / copilotcli

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

MicrosoftAGENTS.md

vscode / agentHost

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

MicrosoftAGENTS.md

vscode / prompts

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

MicrosoftAGENTS.md

vscode / node

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

avelinoAGENTS.md

awesome-go

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-GravitasAGENTS.md

AutoGPT

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

No other project uses it yet

Significant-GravitasReads credentialsAGENTS.md

AutoGPT / autogpt_platform

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

DietrichGebertAGENTS.md

ponytail

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

No other project uses it yet

fReads credentialsAGENTS.md

awesome-chatgpt-prompts

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

twbsAGENTS.md

bootstrap

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

Hugging FaceAGENTS.md

transformers

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

langgeniusReads credentialsAGENTS.md

dify

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

langgeniusAGENTS.md

dify / api

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

langgeniusAGENTS.md

dify / cli

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

langgeniusAGENTS.md

dify / dify-agent

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

langgeniusAGENTS.md

dify / e2e

langgenius/dify/e2e/AGENTS.md

when a required fixture is missing. ## Browser, API, And Contract Boundaries The action under test belongs to the browser. APIs may prepare fixtures, poll persistence, and clean up; they

langgeniusAGENTS.md

dify / web

langgenius/dify/web/AGENTS.md

port. Switch to the Next.js development server (`pnpm -C web dev:next`) only when testing Next.js-specific functionality or investigating behavior that differs from Next.js. - Read `docs/test.md` only for frontend

langflow-aiAGENTS.md

langflow

langflow-ai/langflow/AGENTS.md

make format_frontend # Format TypeScript (biome) make format # Both make lint # mypy type checking ``` ### Testing ```bash make unit_tests # Backend unit tests (pytest, parallel) make unit_tests async=false # Sequential

No other project uses it yet