AGENTS.md examples from real projects

apacheAGENTS.md

dubbo

apache/dubbo/AGENTS.md

will be closed citing the threat model - Matches a known non-finding (§11a) — already documented as a false positive ## For automated security tools The threat model includes a machine-readable

No other project uses it yet

qbittorrentAGENTS.md

qBittorrent

qbittorrent/qBittorrent/AGENTS.md

assistance, but a human must review, take responsibility for, and submit the final changes. ## Document Purpose This document provides policy and guidelines for AI operations. \ Do not expect this file

vimAGENTS.md

vim

vim/vim/AGENTS.md

script files named `test_*.vim`. Screendump expected output lives in `src/testdir/dumps/`. - `runtime/doc/` - user-facing documentation in Vim help format, when updating, also update the Last Change header - `runtime/syntax/generator` - Syntax script

No other project uses it yet

HmbownAGENTS.md

CodeWhale / web

Hmbown/CodeWhale/web/AGENTS.md

truthful state until the complete asset set passes manifest tests. - `AGENT.md` (singular) documents maintainer-owned community automation. Do not expand its authority without Hunter. Choose evidence according to the claim

No other project uses it yet

ToolJetReads credentialsAGENTS.md

ToolJet

ToolJet/ToolJet/AGENTS.md

repository is public; `server/ee/` and `frontend/ee/` are separate private submodules. For public issues, PRs, documentation, and support responses: - Base claims and reproduction steps only on public-repository evidence

ToolJetReads credentialsAGENTS.md

ToolJet / server

ToolJet/ToolJet/server/AGENTS.md

bypass only defers the same failure to CI. ## Testing (Jest) > Tests are documentation first. Describe blocks = table of contents; `it()` = plain English; assertions = response shape. Write failing tests before implementation

outlineAGENTS.md

outline

outline/outline/AGENTS.md

config files** - TypeScript, Vite, Vitest, oxfmt, Oxlint configurations Refer to /docs/ARCHITECTURE.md for detailed architecture documentation. ## Instructions You're an expert in the following areas: - TypeScript - React and React Router - MobX

HmbownAGENTS.md

Codewhale / web

Hmbown/Codewhale/web/AGENTS.md

truthful state until the complete asset set passes manifest tests. - `AGENT.md` (singular) documents maintainer-owned community automation. Do not expand its authority without Hunter. Choose evidence according to the claim

vuetifyjsAGENTS.md

vuetify

vuetifyjs/vuetify/AGENTS.md

vuetify` npm package - `packages/api-generator` — builds API data (props, events, slots, descriptions) for docs - `packages/docs` — documentation site Contributor guide: `packages/docs/src/pages/en/getting-started/contributing.md` Supported browsers: `packages/docs/src/pages/en/getting-started/browser-support.md` ## Branches | Base | For | Docs | |----------|-------------------------------------------------------|--------------------| | `master` | safe bug fixes

No other project uses it yet

schollzAGENTS.md

croc

schollz/croc/AGENTS.md

workflow. GitHub Actions and release operations continue to use the GitHub CLI (`gh`) as documented below. ## Releasing croc Releases are prepared by the **Prepare Release** GitHub Actions workflow

No other project uses it yet

nushellAGENTS.md

nushell

nushell/nushell/AGENTS.md

without adding a pile of new helpers: reuse the helpers that already exist. Document new code. - Don't run `cargo clean`; it forces a full recompile on the next build

pingcapAGENTS.md

tidb

pingcap/tidb/AGENTS.md

format: `PLANS.md` at repository root. - Requirement: keep the ExecPlan updated as a living document while implementation progresses. - Scope: use this for multi-step work where losing context would risk correctness

No other project uses it yet

GitHubAGENTS.md

awesome-copilot

github/awesome-copilot/AGENTS.md

plugin packages (folders with plugin.json) ├── extensions/ # Reusable canvas extension sources (extension.mjs and assets) ├── docs/ # Documentation for different resource types ├── eng/ # Build and automation scripts └── scripts/ # Utility scripts ``` ## Setup Commands ```bash

Yeachan-HeoAGENTS.md

oh-my-claude-sisyphus

Yeachan-Heo/oh-my-claude-sisyphus/AGENTS.md

agent). - Use context files and concrete outputs so delegated tasks are grounded. - Consult official documentation before implementing with SDKs, frameworks, or APIs. - For cleanup or refactor work, write a cleanup

Yeachan-HeoAGENTS.md

oh-my-claude-sisyphus

Yeachan-Heo/oh-my-claude-sisyphus/docs/AGENTS.md

docs User documentation and technical guides for oh-my-claudecode. ## Purpose This directory contains documentation for end-users and developers: - **End-user guides**: How to use oh-my-claudecode features

Yeachan-HeoAGENTS.md

oh-my-claude-sisyphus / skills

Yeachan-Heo/oh-my-claude-sisyphus/skills/AGENTS.md

open question and return grounded, sourced findings | | `external-context/SKILL.md` | external-context | Invoke parallel document-specialist agents for external web searches and documentation lookup | | `autoresearch/SKILL.md` | autoresearch | Stateful single-mission improvement

Yeachan-HeoAGENTS.md

oh-my-claude-sisyphus / src

Yeachan-Heo/oh-my-claude-sisyphus/src/AGENTS.md

Create feature directory in `features/` 2. Export from `features/index.ts` 3. Update `docs/FEATURES.md` with API documentation #### TypeScript Conventions - Use strict mode (`noImplicitAny`, `strictNullChecks`) - Prefer interfaces over type aliases for public APIs

photoprismReads credentialsAGENTS.md

photoprism

photoprism/photoprism/AGENTS.md

what the code was already supposed to do: `Bug` (implemented, but not working as documented), `Enhancement` (new capability on working functionality), `Feature` (entirely new), or `Task` (never fully developed, needs

photoprismAGENTS.md

photoprism / frontend

photoprism/photoprism/frontend/AGENTS.md

Full rules: `specs/frontend/translations.md` §"Case Conventions". ## Focus Management - Dialogs must follow the shared focus pattern documented in `frontend/src/common/README.md`. - Always expose `ref="dialog"` on ` ` overlays, call `$view.enter` and `$view.leave` in `@after-enter

PostHogAGENTS.md

posthog

PostHog/posthog/AGENTS.md

titles. - When a change touches user-facing behavior, an API, a config/setting, or a documented workflow, update an existing doc under `docs/` **whose scope covers that behavior** in the same