AGENTS.md examples from real projects

DeepSeekAGENTS.md

deepseek-harness / workspace

deepseek-ai/deepseek-harness/snapshots/session/agent-instructions-budget-chains/workspace/.dsh/AGENTS.md

project. Reply in short, plain sentences and state the result first. Run the narrowest test that covers a change before reporting it as done. Never commit, push, or delete branches

No other project uses it yet

DeepSeekAGENTS.md

deepseek-harness / website

deepseek-ai/deepseek-harness/website/AGENTS.md

block because tab switching is unavailable; the [code-group adapter](.vitepress/code-groups.ts) and its [focused tests](tests/code-groups.spec.ts) own this behavior. Long tables with at least ten data rows receive independent text

No other project uses it yet

NousResearchAGENTS.md

hermes-agent / agent

NousResearch/hermes-agent/agent/AGENTS.md

CHILD_ENV_MARKER` valued as the fenced Kanban board root, not a bare flag. ## Tests Loop/phase tests go in `tests/agent/`; patch the binding the phase actually reads (siblings often `from

No other project uses it yet

NousResearchAGENTS.md

hermes-agent / plugins

NousResearch/hermes-agent/plugins/AGENTS.md

process warning, documented replacement + migration note, ≥ 2 subsequent minor releases before removal. - Compat tests load **frozen plugins through the real discovery path** and assert outcomes — never exact registry/catalog counts, source

NousResearchAGENTS.md

hermes-agent / pm

NousResearch/hermes-agent/pm/AGENTS.md

plugin may move a transitive core package within core's declared ranges (`tests/pm/test_workspace_build_inputs.py::test_plugin_can_move_compatible_transitive_but_not_exact_requirement`). Plugin `python_dependencies` follow the plugin

NousResearchAGENTS.md

hermes-agent / tests

NousResearch/hermes-agent/tests/AGENTS.md

tests/ — how Hermes tests are written and run Applies on top of the root `AGENTS.md`. Read it before adding or changing any test. ## Running tests **ALWAYS use `scripts/run_tests.sh`**, never bare

NousResearchAGENTS.md

hermes-agent / web

NousResearch/hermes-agent/web/AGENTS.md

surface; a new surface is a new `web_routers/ .py`, not a growing `web_server.py`. - Tests: Python in `tests/hermes_cli/` (routers, pty bridge); JS in the `web/` vitest suite. Python tests must

affaan-mAGENTS.md

ECC

affaan-m/ECC/AGENTS.md

Core Principles 1. **Agent-First** — Delegate to specialized agents for domain tasks 2. **Test-Driven** — Write tests before implementation, 80%+ coverage required 3. **Security-First** — Never compromise on security; validate

No other project uses it yet

TheAlgorithmsAGENTS.md

Python

TheAlgorithms/Python/AGENTS.md

change code and its doctests in the same PR.** If you're only updating tests, say so and touch nothing else. ## Code conventions (enforced by CI) - **Formatting & linting:** `ruff

No other project uses it yet

sstAGENTS.md

opencode

sst/opencode/AGENTS.md

origin/dev`, target PRs at `dev`, and diff against `origin/dev` unless told otherwise. ## Live TUI Testing - Run `bun run dev:live` from a development worktree to test its TUI against

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

No other project uses it yet

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

No other project uses it yet

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

No other project uses it yet

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

No other project uses it yet

instructkrAGENTS.md

claw-code / rust

instructkr/claw-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

claw-code / src

instructkr/claw-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

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

No other project uses it yet

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

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

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