AGENTS.md examples from real projects

DeepSeekAGENTS.md

deepseek-harness / benchmarks

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

local diagnostics remain beside their owners and use the `.perf.ts` suffix instead of joining `test:bench`. - Organize benchmarks by measured user path, one directory per path. Do not mirror

DeepSeekAGENTS.md

deepseek-harness

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

widen that scope. A reference may be exhaustive only about its own subject. Testing mechanisms, fixtures, and harnesses belong at the lowest owning level; higher documents link there. Classify every

DeepSeekAGENTS.md

deepseek-harness

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

steps on the default POSIX shell; shared entrypoints are Node scripts. Test and production jobs use separate `desktop-test` and `desktop-production` approval Environments after a credential-free preparation

DeepSeekAGENTS.md

deepseek-harness / system

deepseek-ai/deepseek-harness/native/system/AGENTS.md

implementation. - Runtime binary selection has no environment-variable overrides. `NALR_REQUIRE_LANDLOCK` is a test-only enforcement requirement. - There is no install-time compile fallback. Missing Landlock binaries probe unusable

No other project uses it yet

DeepSeekAGENTS.md

deepseek-harness / packages

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

global service store ([postmortem](../docs/postmortem/0001-acp-default-export-drops-inject.md)). - **Product-visible plugins require a non-unit REAL-composition test.** Hand-built `ctx.plugin(...)` suites are insufficient. Boot test-only `cordis.yml` through the Loader and app/process

DeepSeekReads credentialsAGENTS.md

deepseek-harness / client

deepseek-ai/deepseek-harness/packages/client/AGENTS.md

committed render position. Production code never calls the factory or `.create()` outside registration; tests do (that is the sanctioned zero-machinery path). 7. **inject returns plain data and callbacks** from

DeepSeekAGENTS.md

deepseek-harness / experimental

deepseek-ai/deepseek-harness/packages/experimental/AGENTS.md

shipped compositions in CI. Experimental packages may depend on release packages and each other. Tests may use experimental packages through `devDependencies`; examples may load them explicitly. - Experimental status does

No other project uses it yet

DeepSeekAGENTS.md

deepseek-harness / schedule

deepseek-ai/deepseek-harness/packages/schedule/AGENTS.md

delivery. - Keep recurrence arithmetic pure. Production uses platform wall time and segmented timers; tests use explicit samples or restored fake timers

No other project uses it yet

DeepSeekAGENTS.md

deepseek-harness / scripts

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

ownership gates use syntax-aware discovery, guard against an empty or narrowed corpus, and test every admitted/excluded form that changes their detection boundary. Script specs run in forked workers beside

DeepSeekAGENTS.md

deepseek-harness / snapshots

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

AGENTS.md — Recorded-session snapshots This tree contains only tests whose committed session JSONL is replay input and expected persisted output. Keep non-session ARIA, geometry, generator, CLI, and unit expected

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

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

NousResearchReads credentialsAGENTS.md

hermes-agent

NousResearch/hermes-agent/AGENTS.md

refactors; extending before duplicating (3+ PRs in one category → an ABC + orchestrator); behaviour-contract tests; E2E with real imports against a temp `HERMES_HOME` for resolution, config, security

NousResearchReads credentialsAGENTS.md

hermes-agent / cron

NousResearch/hermes-agent/cron/AGENTS.md

root, so a child working against a scratch `HERMES_HOME` keeps a writable board. ## Tests `tests/cron/`, `tests/hermes_cli/test_kanban*.py`, `tests/tools/test_kanban*.py`. Schedule parsing and catch-up windows are pure functions — test

No other project uses it yet

NousResearchReads credentialsAGENTS.md

hermes-agent / gateway

NousResearch/hermes-agent/gateway/AGENTS.md

exists. A sealed native stream is a regular message — `chat.update` works (live-verified). Contract tests: `tests/gateway/test_stream_final_contract.py` (mutation-checked). Slack ground truth: `chat.*Stream` speaks STANDARD markdown, not mrkdwn; `stopStream.markdown_text

NousResearchReads credentialsAGENTS.md

hermes-agent / hermes_cli

NousResearch/hermes-agent/hermes_cli/AGENTS.md

ROOT_KEYS`). For a new key: `rg -n '" "' hermes_cli/config_defaults.py` AND `rg -n ' ' --glob '!tests' .` both hit, and one invariant test sets it in a temp `config.yaml` and asserts

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

Developer-only tools (`just`) are optional packages in `pm.testenv.DEVELOPER_TOOLS`: the `--test-environment` install provisions those the lockfile pins; a user install or desktop bundle never does. Use `pm.build_environment

NousResearchReads credentialsAGENTS.md

hermes-agent / skills

NousResearch/hermes-agent/skills/AGENTS.md

every call — ship a helper script and reference it by skill-relative path. 7. **Tests at `tests/skills/test_ _skill.py`**, stdlib + pytest + `unittest.mock` only, no live network. Run `scripts/run_tests.sh tests/skills/test_ _skill.py

No other project uses it yet