AGENTS.md examples from real projects

sgl-projectAGENTS.md

sglang

sgl-project/sglang/docs/AGENTS.md

Build and maintain the SGLang documentation site and integrated cookbook using Mintlify. Use when

morlutoAGENTS.md

rea

morluto/rea/AGENTS.md

fast`: cached typecheck/lint and the pre-push check. - `npm run docs:check`: validate generated documentation. Use relevant checks for the change. The complete local gate, `npm run check

moltbotAGENTS.md

moltbot

moltbot/moltbot/AGENTS.md

only at egress (logs.tail, diagnostics/support bundles, remote/OTel export); never log message/tool content. - Plugins use documented `openclaw/plugin-sdk/*` contracts, manifest metadata, public/local barrels; never core internals or another plugin's private files

moltbotAGENTS.md

moltbot / ui

moltbot/moltbot/ui/AGENTS.md

pointer cursors; state-changing controls: default arrow. - Colors: use `src/styles/base.css` tokens. - `main.runtime.ts` injects `components/kbd.css` document-wide; renderers never import it. Never JS-import a sheet `styles.css` already ships from

steipeteAGENTS.md

warelay

steipete/warelay/AGENTS.md

only at egress (logs.tail, diagnostics/support bundles, remote/OTel export); never log message/tool content. - Plugins use documented `openclaw/plugin-sdk/*` contracts, manifest metadata, public/local barrels; never core internals or another plugin's private files

molt-botAGENTS.md

clawdbot

molt-bot/clawdbot/AGENTS.md

beta, and nightly code are not shipped contracts. ## Runtime and code safeguards - Plugins use documented `openclaw/plugin-sdk/*` contracts, manifest metadata, and public/local barrels, never core internals or another plugin's private

molt-botAGENTS.md

clawdbot

molt-bot/clawdbot/docs/AGENTS.md

root `AGENTS.md`. - CI verifies JSON5 and JSON config fences that look like whole `openclaw.json` documents against the schema. `pnpm docs:check-config-examples` runs that verification. Deliberately partial or legacy

obraAGENTS.md

superpowers

obra/superpowers/AGENTS.md

what produced a change in order to weigh it: agent-generated content reasoned from documentation is held to a different bar than work grounded in a real session. Contributions that

No other project uses it yet

DeepSeekReads credentialsAGENTS.md

deepseek-harness

deepseek-ai/deepseek-harness/AGENTS.md

plugin Cordis agent harness. Read [docs/architecture.md](docs/architecture.md) before changing `packages/`; follow [docs/AGENTS.md](docs/AGENTS.md) for documentation. ## Pre-stable APIs and released Session data Public APIs are pre-stable; update every consumer

DeepSeekAGENTS.md

deepseek-harness / notes

deepseek-ai/deepseek-harness/.agents/notes/AGENTS.md

proposals and decision records that preserve rationale, alternatives, consequences, and required verification. Follow the [documentation standard](../../docs/AGENTS.md) and the [Agent Note rules](README.md). **Every new Agent Note triggers a supersession

DeepSeekAGENTS.md

deepseek-harness / archived

deepseek-ai/deepseek-harness/.agents/notes/archived/AGENTS.md

repair, delete, or move a sealed artifact; use an active Agent Note or current documentation for new decisions and facts. The archival change may only relocate a complete English/Chinese/sidecar triplet

DeepSeekAGENTS.md

deepseek-harness / implemented

deepseek-ai/deepseek-harness/.agents/notes/implemented/AGENTS.md

Implemented Agent Notes These Agent Notes describe shipped decisions. Follow the [root instructions](../../../AGENTS.md), [documentation standard](../../../docs/AGENTS.md), and [Agent Note format](../README.md#the-file-format); `verify-agent-note-format` gates

DeepSeekAGENTS.md

deepseek-harness

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

AGENTS.md — The documentation standard This file defines document structure, Markdown tiers, writing rules, and `verify-doc-budgets` ceilings. Use [dsh-doc](../.agents/skills/dsh-doc/SKILL.md) for placement and validation, and [dsh-prose-standard

DeepSeekAGENTS.md

deepseek-harness / packages

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

subsystem ownership through a canonical English page link or justified [exemption](../scripts/verify-subsystem-pages.ts). - Package READMEs document model, token, and KV-cache effects using the [canonical Model Experience format](../docs/cookbook/adding-a-package.md#4-write

DeepSeekReads credentialsAGENTS.md

deepseek-harness / client

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

Definition republishes the block when an observed answer changes. Transient file-read and document-preview content may also carry `Uint8Array`: published buffers are borrowed read-only, copied before Worker transfer

DeepSeekAGENTS.md

deepseek-harness / experimental

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

through `devDependencies`; examples may load them explicitly. - Experimental status does not relax engineering, security, documentation, lifecycle, testing, or snapshot requirements. - Publishing an experimental package does not promote

No other project uses it yet

DeepSeekAGENTS.md

deepseek-harness / website

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

AGENTS.md — Documentation website adapter Follow the [root instructions](../AGENTS.md), the [documentation standard](../docs/AGENTS.md), and the [documentation workflow](../.agents/skills/dsh-doc/SKILL.md). ## Keep documentation content out of this tree `website/` owns only VitePress configuration

NousResearchAGENTS.md

hermes-agent / plugins

NousResearch/hermes-agent/plugins/AGENTS.md

VERSION`, a manifest-wide native `api:` match, or version literals on unrelated payloads. Documented surfaces stay additive: - Hook payload data is added as **keyword fields**; callbacks are signature-inspected

affaan-mAGENTS.md

ECC

affaan-m/ECC/AGENTS.md

Playwright testing | Critical user flows | | refactor-cleaner | Dead code cleanup | Code maintenance | | doc-updater | Documentation and codemaps | Updating docs | | cpp-reviewer | C/C++ code review | C and C++ projects | | cpp-build

No other project uses it yet

n8n-ioReads credentialsAGENTS.md

n8n

n8n-io/n8n/AGENTS.md

voice, and one instruction for each sentence - **JSDoc on `@Env(...)` config properties is public documentation.** The docs team exports these comments into the environment variable reference on docs.n8n.io. Write them