AGENTS.md examples from real projects

ag-ui-protocolAGENTS.md

ag-ui

ag-ui-protocol/ag-ui/AGENTS.md

affected`) instead of using the underlying tooling directly - You have access to the Nx MCP server and its tools, use them to help the user - When answering questions about

No other project uses it yet

zephyrproject-rtosAGENTS.md

zephyr

zephyrproject-rtos/zephyr/AGENTS.md

last six months of issues and PRs are also searchable through the project's MCP server, `https://zephyrproject.mcp.kapa.ai` (`doc/develop/tools/kapa_ai.rst`); its answers are generated and must be verified against the tree

a2ui-projectAGENTS.md

a2ui

a2ui-project/a2ui/AGENTS.md

release scripts (`scripts/`). - **`samples/`**: Ready-to-run demo agents utilizing Python ADK (`agent/adk/`), MCP server (`agent/mcp/`), and sample clients (`client/lit/`, `client/angular/`, `client/react/`, `client/flutter/`). - **`swift/`**: Native Apple implementation including core state

GoogleAGENTS.md

A2UI

google/A2UI/AGENTS.md

release scripts (`scripts/`). - **`samples/`**: Ready-to-run demo agents utilizing Python ADK (`agent/adk/`), MCP server (`agent/mcp/`), and sample clients (`client/lit/`, `client/angular/`, `client/react/`, `client/flutter/`). - **`swift/`**: Native Apple implementation including core state

MODSetterReads credentialsAGENTS.md

SurfSense

MODSetter/SurfSense/AGENTS.md

portal](docs/architecture/license/portal.md) in `license/`, its `mailer/`, and `plugins/`, which holds SurfSense's own plugin servers ([plugin host](docs/architecture/plugin-host.md)) and the [registry](docs/architecture/plugin-registry.md); `plugins/bundles/` holds the earlier, local design

Arindam200Reads credentialsAGENTS.md

awesome-ai-apps

Arindam200/awesome-ai-apps/AGENTS.md

args": ["-y", "@modelcontextprotocol/server-github"], "env": {"GITHUB_PERSONAL_ACCESS_TOKEN": os.environ["TOKEN"]} } ) as server: agent = Agent(mcp_servers=[server], ...) ``` Example: `mcp_ai_agents/github_mcp_agent/main.py`, `mcp_ai_agents/mcp_starter/main.py` ### Framework-Specific Patterns **Agno Framework** (most

opensandbox-groupAGENTS.md

OpenSandbox

opensandbox-group/OpenSandbox/AGENTS.md

MCP SDKs plus generated clients - `specs/`: public OpenAPI contracts and examples - `kubernetes/`: Kubernetes operator, CRDs, task-executor, and Kind e2e tests - `manifests/charts/`: Helm charts (base, controller, server, ingress-gateway, node

triggerdotdevAGENTS.md

trigger.dev

triggerdotdev/trigger.dev/AGENTS.md

analytics) + PostgreSQL (state) ### Apps - **apps/webapp**: Remix 2.17.4 app - main API, dashboard, orchestration. Uses Express server. - **apps/supervisor**: Manages task execution containers (Docker/Kubernetes). ### Public Packages - **packages/trigger-sdk** (`@trigger.dev/sdk`): Main SDK for writing

No other project uses it yet

mobile-dev-incReads credentialsAGENTS.md

Maestro

mobile-dev-inc/Maestro/AGENTS.md

Shared command/data models (used by `maestro-orchestra/` and consumers). | | `maestro-cli/` | CLI entry point + MCP server. Mixed Kotlin (~100 files) + Swift (~56 files for iOS-related CLI bits). | | `maestro-utils

No other project uses it yet

ParadevAIReads credentialsAGENTS.md

Paradev

ParadevAI/Paradev/AGENTS.md

reach its tools through `/mcp/plugins/ / ` on the API, which proxies to the vendor's MCP server or, for the plugins named in the `SUPERSET_HOSTED_PLUGINS` constant, serves them from

spreeAGENTS.md

spree

spree/spree/AGENTS.md

/dashboard` and seller panel at `/sellers` from the Rails node | | `spree/mcp` | `spree_mcp` — MCP server for the back office, under the Admin API's tenancy and permission rules | | `spree/opentelemetry` | `spree

No other project uses it yet

spreeAGENTS.md

spree / spree

spree/spree/spree/AGENTS.md

agent tools **Every new back-office workflow or feature also ships in the MCP server** — anything a merchant can do in the admin dashboard or Admin API, an agent

No other project uses it yet

open-metadataAGENTS.md

OpenMetadata

open-metadata/OpenMetadata/AGENTS.md

operator/` — Kubernetes operator - `openmetadata-integration-tests/` — backend API integration tests (`*IT.java`) - `openmetadata-mcp/` — MCP server - `openmetadata-ui-core-components/` — canonical React component library - `openmetadata-ui/src/main/resources/ui/` — React frontend application - `openmetadata

No other project uses it yet

storytoldDeletes or force-pushesAGENTS.md

lightcraft

storytold/lightcraft/AGENTS.md

crates/engine`): id, label, menu path, shortcut, params, enabled(), run(). UI, CLI, control channel and MCP all dispatch by id. Every slider is a `develop` control spec. - **Long-running work shows

No other project uses it yet

akitaonrailsAGENTS.md

ai-memory

akitaonrails/ai-memory/AGENTS.md

version is `workspace.package.version` in `Cargo.toml`. - **Async runtime:** `tokio` (full features). - **MCP/HTTP:** `rmcp` 3.8 (server SDK; MCP 2026-07-28 plus the legacy initialize handshake) + `axum` 0.8 for MCP HTTP, hooks

apifyAGENTS.md

apify-mcp-server

apify/apify-mcp-server/AGENTS.md

Apify MCP server TypeScript, ES modules. Runs in two modes: **stdio** (local CLI clients, `stdio.ts`) and **HTTP Streamable** (`dev_server.ts`). **Before implementing**: work from an issue that is assigned or explicitly

No other project uses it yet

apifyAGENTS.md

apify-mcp-server / src

apify/apify-mcp-server/src/AGENTS.md

index_internals_test_kit.ts` — the separate `./internals/test-kit.js` surface for `tests/test_kit/**`'s own self-reference imports only; apify-mcp-server-internal doesn't consume it, don't add anything here it does. - `stdio.ts

No other project uses it yet

prowler-cloudAGENTS.md

prowler

prowler-cloud/prowler/AGENTS.md

conventions | [SKILL.md](skills/prowler-ui/SKILL.md) | | `prowler-sdk-check` | Create new security checks | [SKILL.md](skills/prowler-sdk-check/SKILL.md) | | `prowler-mcp` | MCP server tools and models | [SKILL.md](skills/prowler-mcp/SKILL.md) | | `prowler-test-sdk` | SDK testing (pytest + moto) | [SKILL.md](skills/prowler-test-sdk/SKILL.md

No other project uses it yet

prowler-cloudAGENTS.md

prowler

prowler-cloud/prowler/docs/AGENTS.md

group is subscription-gated. One sanctioned exception: the Prowler MCP group is marked because the hosted server at `mcp.prowler.com` includes tools for Prowler Cloud-specific features, and its overview page

No other project uses it yet

prowler-cloudAGENTS.md

prowler / mcp_server

prowler-cloud/prowler/mcp_server/AGENTS.md

Prowler MCP Server - AI Agent Ruleset > **Skills Reference**: See [`prowler-mcp`](../skills/prowler-mcp/SKILL.md) ## Auto-invoke Skills When performing these actions, ALWAYS invoke the corresponding skill FIRST: | Action | Skill | |--------|-------| | Add changelog entry

No other project uses it yet