AGENTS.md examples from real projects

homeassistant-aiAGENTS.md

ha-mcp / homeassistant-addon-webhook-proxy

homeassistant-ai/ha-mcp/homeassistant-addon-webhook-proxy/AGENTS.md

stable + dev) ## What it is A thin app that does NOT run an MCP server. It discovers a running ha-mcp server app (stable `ha_mcp`, then dev `ha_mcp

No other project uses it yet

homeassistant-aiAGENTS.md

ha-mcp / tests

homeassistant-ai/ha-mcp/tests/AGENTS.md

skips everywhere else. `src/e2e/workflows/filesystem/test_tools_entry_absent.py` is the module that carries it. The server entry also registers the `ha_mcp_tools/*` WebSocket surface (#2291), so on the two `embedded` shapes the shared

debbaAGENTS.md

tabularis

debba/tabularis/AGENTS.md

only module behind the `desktop` cargo feature; `cargo build --no-default-features` builds the server without Tauri. - **A desktop command is a thin wrapper over `application/`.** Implement the behaviour there

No other project uses it yet

hahwulAGENTS.md

dalfox

hahwul/dalfox/AGENTS.md

/only-discovery/result rendering), `poc.rs`, `postprocess.rs`, `logging.rs` - `src/cmd/mod.rs`: shared `error_codes` constants (used by CLI + server + MCP) - `src/config.rs`: config schema + precedence (`apply_to_scan_args_if_default`) - `src/scanning/`: reflection/DOM checks, AST integration

hahwulAGENTS.md

dalfox

hahwul/dalfox/docs/AGENTS.md

invariants in the repo-root `AGENTS.md`. Treat it as a fourth interface alongside CLI / server / MCP. - **Output formats**: `src/scanning/result/` and `src/cmd/scan/output.rs` (output routing). Keep `docs/content/guide/output.md` aligned. - **Stage names**: see `src/lib.rs

WaishnavAGENTS.md

devspace

Waishnav/devspace/AGENTS.md

currently provides mature local coding primitives. DevSpace wraps those primitives in a Streamable HTTP MCP server and adds the product-specific boundaries around them: approved roots, workspace state, instructions, process

Model Context ProtocolAGENTS.md

go-sdk

modelcontextprotocol/go-sdk/AGENTS.md

Packages - `mcp`: The core package defining the primary APIs for constructing and using MCP clients and servers. This is where most logic resides. - `jsonrpc`: Provides the JSON-RPC 2.0 transport

No other project uses it yet

MistralAGENTS.md

mistral-vibe

mistralai/mistral-vibe/AGENTS.md

Agent Client Protocol; `vibe/setup` holds auth and onboarding config shared by the app server and `vibe-acp`. Tests live in `tests/` with autouse fixtures in `conftest.py` and test doubles

zerx-labAGENTS.md

FluxDown

zerx-lab/FluxDown/AGENTS.md

native/mobile`）共享核心；NAS / 服务器 = `fluxdown-agent --server` + `fluxdownd`（React Web SPA 经 agent `/rpc`）。另有 CLI、WXT 浏览器扩展、Tampermonkey 用户脚本、JS 插件系统与 MCP / REST / aria2 API。旧 Flutter 工程

pollinationsReads credentialsAGENTS.md

pollinations

pollinations/pollinations/AGENTS.md

React frontend - `packages/sdk/` — `@pollinations/sdk` (client + React hooks) - `packages/mcp/` — shared handlers for the hosted stateless MCP server (see `packages/mcp/AGENTS.md`) - `shared/` — auth, registry, IP queue; `shared/registry/` holds model registries - `apps/` — Applications maintained

homarr-labsAGENTS.md

homarr

homarr-labs/homarr/AGENTS.md

maintainer explicitly runs through `homarr-triage` keep that disclaimer as their first line. ## MCP servers The [Homarr Mantine plugin](plugins/homarr-mantine/plugin.json) bundles the UI skill and pinned documentation MCP server. `.agents/plugins/marketplace.json

Marker-Inc-KoreaReads credentialsAGENTS.md

AutoRAG

Marker-Inc-Korea/AutoRAG/AGENTS.md

discrawl, msgvault, …) in place. No forced ingestion into a central index, no third-party server holding a copy of the corpus. Results carry source-native identities (`/kakao/ /chunks/ `), and secrets

chakra-uiAGENTS.md

zag

chakra-ui/zag/AGENTS.md

pnpm test` | | Start React dev server | `pnpm start-react` (port 3000) | | Start Preact dev server | `pnpm start-preact` (port 5173) | | E2E tests (React) | `pnpm e2e-react` | | E2E tests (Preact) | `pnpm

gdamoreAGENTS.md

tcell

gdamore/tcell/AGENTS.md

gopls` MCP server by default when working on Go code in this repository, unless I explicitly

apacheAGENTS.md

iggy

apache/iggy/AGENTS.md

types (IggyDuration, IggyTimestamp, ...) │ ├── binary_protocol/ Wire format (stable) │ ├── configs/ Config plumbing + ConfigEnv derive │ ├── ai/mcp/ MCP server │ ├── bench/ Benchmark suite │ ├── integration/ Cross-crate integration tests │ ├── simulator/ Deterministic simulator │ ├── consensus/ Raft (Miri

transformerlabAGENTS.md

transformerlab-app

transformerlab/transformerlab-app/AGENTS.md

local development: ```bash cd lab-sdk && pip install -e . ``` Then restart the API server. This is a common gotcha — the API imports the *installed* `lab` package, not the source tree

totec448-specReads credentialsAGENTS.md

chat-on-steroids

totec448-spec/chat-on-steroids/AGENTS.md

browser page | MCP via public tunnel | native UI and conversation state v | MAIN: fiber.js + usage.js Core / Desktop / Plugins | isolated: chatgpt-dom.js + content.js | secret path per surface v server -> registrar -> kernel background.js

icip-casAGENTS.md

PPTAgent

icip-cas/PPTAgent/AGENTS.md

generation and evaluation library, still shipped in the package and still used for the MCP server entrypoint `pptagent-mcp`. When making changes, treat `deeppresenter` as the primary product surface unless

facebookAGENTS.md

memlab

facebook/memlab/AGENTS.md

change it (write a leak test scenario, analyze a heap snapshot, set up the MCP server), read [AI.md](./AI.md) and the Agent Skills under [`plugins/memlab/skills/`](./plugins/memlab/skills) instead. ## Repository layout memlab

clideyAGENTS.md

whodb

clidey/whodb/AGENTS.md

browser AI agent feature (under `ee/`), NOT the coding-agent (Claude/Codex) configuration or any MCP server. When in doubt, ask which is meant before acting. ## Non-Negotiable Rules 1. **GraphQL

No other project uses it yet