AGENTS.md examples from real projects

compiler-explorerReads credentialsAGENTS.md

compiler-explorer

compiler-explorer/compiler-explorer/AGENTS.md

hooks (`npm run check-frontend-imports`) - Violations will cause build failures and prevent commits ## Security Review Calibration - Internal, CE-controlled endpoints (e.g. the conan library server) are not hostile: treat

No other project uses it yet

browser-useAGENTS.md

browser-harness

browser-use/browser-harness/AGENTS.md

routine PR gates. - First-time install / blocked Chrome: follow `install.md` (`chrome://inspect/#remote-debugging`). # Security - Do not commit secrets, Browser Use Cloud tokens, or session cookies. - Prefer the smallest change

No other project uses it yet

langbot-appReads credentialsAGENTS.md

LangBot

langbot-app/LangBot/AGENTS.md

note. - Code comments and docstrings must be English. Commit message format: ` ( ): `. - Keep compatibility and security in mind; LangBot serves both self-hosted/community and toB deployments. ## Unified API (Workspace

wledDeletes or force-pushesAGENTS.md

WLED

wled/WLED/AGENTS.md

description - in addition to comments markers in the source code (see Comments section). ### Security Hardening When writing or reviewing code in `wled00/`, `usermods/`, `wled00/data/`, or `.github/workflows/`, consult `docs/hardening.instructions.md` (concise checklist

eggjsDeletes or force-pushesAGENTS.md

egg

eggjs/egg/AGENTS.md

loader): ensure middleware order` - keep PR descriptions clear about motivation, scope, and test evidence ## Security And Config - review `SECURITY.md` before handling vulnerability-related work - do not commit secrets, credentials

facebookAGENTS.md

yoga

facebook/yoga/AGENTS.md

just that platform. Choose the appropriate type: `[Breaking]`, `[Added]`, `[Changed]`, `[Deprecated]`, `[Removed]`, `[Fixed]`, or `[Security]`. If the change truly has no user-visible effect, such as a test-only

lidge-junPipes a download into a shellAGENTS.md

opencodex

lidge-jun/opencodex/AGENTS.md

gitlink may be tracked anywhere, and neither the vendored reference clones nor the security triage excised before publication may reappear in the index. Both were driven red once to prove

lidge-junAGENTS.md

opencodex

lidge-jun/opencodex/.github/AGENTS.md

instructions This file applies to `.github/` and inherits the repository-wide rules in `/AGENTS.md`. ## Security boundary Every workflow, ownership, branch-enforcement, release, or repository-automation change requires explicit security review

lidge-junAGENTS.md

opencodex / gui

lidge-jun/opencodex/gui/AGENTS.md

provided by the current stack or a small local implementation. - Dependency changes require explicit security review. - Update `docs-site/` when dashboard behavior, setup, or configuration changes for users. ## Failure mode

lidge-junAGENTS.md

opencodex / scripts

lidge-jun/opencodex/scripts/AGENTS.md

Changes to release, packaging, dependency-installation, credential, or repository-automation scripts require explicit security review. ## Implementation rules - Preserve Linux, macOS, and Windows behavior. Do not add shell-specific assumptions

lidge-junAGENTS.md

opencodex / src

lidge-jun/opencodex/src/AGENTS.md

relevant to that adapter. - Authentication, OAuth, token, credential, management API, and CORS changes are security-boundary changes. ## Tests and validation - Place focused regression coverage near the existing tests

lidge-junAGENTS.md

opencodex / structure

lidge-jun/opencodex/structure/AGENTS.md

devlog/`. - Superseded or alternative reasoning belongs in `decisions/`, not in the doc body. - Unreleased security findings belong in scratch space and nowhere in this repository. The rule in the root

uikitAGENTS.md

uikit

uikit/uikit/AGENTS.md

latest versioned release. Add entries under non-empty `### Added`, `### Changed`, `### Deprecated`, `### Removed`, `### Fixed`, or `### Security` categories. - Never commit generated `dist` files. - Do not modify SCSS files; they are generated from

No other project uses it yet

arc53Reads credentialsAGENTS.md

DocsGPT

arc53/DocsGPT/AGENTS.md

bash vale . ``` ## Repository map - `docsgpt/`: Flask backend, API routes, agent logic, retrieval, parsing, security, storage, Celery worker, and WSGI entrypoints. - `tests/`: backend unit/integration tests and test-only Python dependencies. - `frontend

LangChainReads credentialsAGENTS.md

langchainjs

langchain-ai/langchainjs/AGENTS.md

This document provides guidance for AI coding agents working with the LangChain.js codebase. ## Corridor security analysis When Corridor's `analyzePlan` tool is available, create a plan and use the tool

No other project uses it yet

emcie-coAGENTS.md

parlant

emcie-co/parlant/AGENTS.md

support enterprise, large-scale use cases, where SLAs, stability and security are paramount. That is a bar every change has to clear, not the audience Parlant is built around. Most

zhanymkanovReads credentialsAGENTS.md

fastapi-best-practices

zhanymkanov/fastapi-best-practices/AGENTS.md

MINUTES: int = 5 REFRESH_TOKEN_KEY: str REFRESH_TOKEN_EXP: timedelta = timedelta(days=30) SECURE_COOKIES: bool = True auth_settings = AuthConfig() ``` ## Dependencies ### Use Annotated, not default-arg `Depends(...)` `Annotated

larksuiteAGENTS.md

cli

larksuite/cli/AGENTS.md

dependencies for straightforward behavior. YAGNI never overrides explicit requirements or output, error, path, security, compatibility, and data-safety contracts. If a deliberately limited solution has a real ceiling, document

No other project uses it yet

verdaccioReads credentialsAGENTS.md

verdaccio

verdaccio/verdaccio/AGENTS.md

tags, and Node.js policy for every release line live in [VERSIONS.md](./VERSIONS.md); the security policy in [SECURITY.md](./SECURITY.md). The other branches of this repository: | Branch | Role | | -------- | -------------------------------------------------------------------------------------------------------- | | `master` | 9.x next

apacheAGENTS.md

brpc

apache/brpc/AGENTS.md

change, list tests run, note platform or dependency assumptions, and pass GitHub Actions. ## Security & Configuration Tips Read `SECURITY.md` before reporting vulnerabilities. Avoid committing build directories, local paths, credentials, or machine

No other project uses it yet