AGENTS.md examples from real projects

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

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

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

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

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

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

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

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

No other project uses it yet

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

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

IsmaelMartinezAGENTS.md

teams-for-linux

IsmaelMartinez/teams-for-linux/AGENTS.md

Portfolio dashboard:** https://ismaelmartinez.github.io/repo-butler/ **Consumer guide:** https://github.com/IsmaelMartinez/repo-butler/blob/main/docs/consumer-guide.md ### Querying Reginald (the butler MCP server) To query your repo's health tier, governance findings, and portfolio data from

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

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

aldinokemalReads credentialsAGENTS.md

go-whatsapp-web-multidevice

aldinokemal/go-whatsapp-web-multidevice/AGENTS.md

WhatsApp API server using whatsmeow, Fiber, and SQLite. The Go module and local runtime directory are `src/`. `rest` also mounts MCP at `/mcp` when enabled; both transports share the same

mock-serverAGENTS.md

mockserver

mock-server/mockserver/AGENTS.md

response builder, provider codecs, streaming physics, conversation matchers, isolation, MCP tools, or LLM dashboard | | [docs/code/ai-protocol-mocking.md](docs/code/ai-protocol-mocking.md) | Before modifying MCP/A2A server mocking, SSE/WebSocket/JSON-RPC mock responses, or AI protocol handlers | | [docs/code/llm-codec-fixtures.md](docs/code/llm-codec-fixtures.md

mvanhornAGENTS.md

cli-printing-press

mvanhorn/cli-printing-press/AGENTS.md

runtime walker in `internal/mcp/cobratree/` mirrors the Cobra tree at server start and registers every user-facing command as an MCP tool unless one of these applies: 1. Commands annotated `cmd.Annotations

tfutilsAGENTS.md

tfenv

tfutils/tfenv/AGENTS.md

repos/tfutils/tfenv/...` for operations not covered by high-level `gh` commands. The GitHub MCP server may supplement `gh` where proven reliable, but must never be on the critical path. --- ## Work Type