AGENTS.md examples from real projects

PydanticReads credentialsAGENTS.md

pydantic-ai / workflows

pydantic/pydantic-ai/.github/workflows/AGENTS.md

green while never having run. That is not hypothetical: the former `pydantic-ai-ui-security-review` shipped this way and its agent never fired once, reporting false-green on every

PydanticReads credentialsAGENTS.md

pydantic-ai / realtime

pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/realtime/AGENTS.md

reimplement or filter above it. A reimplemented policy layer that drifts is a security bug, not a style problem: the realtime approval-bypass was exactly this. - When behavior differs from

wekanAGENTS.md

wekan

wekan/wekan/AGENTS.md

pull request ITSELF is the participant, and is named.** GitHub CodeQL filing a security fix, Copilot Autofix, Dependabot raising a dependency bump: nobody wrote those, so crediting a human would

gravitationalAGENTS.md

teleport

gravitational/teleport/AGENTS.md

AGENTS.md ## Review Guidelines - Focus only on critical security, reliability, performance, and scalability issues. - Ignore style, performance micro-optimizations, and readability nits unless they are tied to a significant failure ### What

refactoringhqDeletes or force-pushesAGENTS.md

tolaria

refactoringhq/tolaria/AGENTS.md

unavailable after one retry, or when satisfying the rule is technically impossible without increasing security or data-loss risk. The repository owner is the sole approver. Before proceeding, record

linkwardenReads credentialsAGENTS.md

linkwarden

linkwarden/linkwarden/AGENTS.md

user-supplied URL goes through `safeFetch` / the SSRF helpers. This is a security boundary; do not bypass it. - Server-side data access belongs in a controller under `apps/web/lib/api/controllers/`, client-side

No other project uses it yet

AstralAGENTS.md

ty

astral-sh/ty/AGENTS.md

Repository ## Security reviews For reviews of this repository's GitHub automation, CI, and release process, use the [GitHub repository threat model](agents/references/repository-threat-model.md). The `ruff` submodule pins ty's Rust source

GoogleAGENTS.md

gvisor

google/gvisor/AGENTS.md

assumptions by writing syscall tests to verify Linux behavior from a black-box perspective. #### Security first All changes are reviewed for security. gVisor's design and architecture ensures that

sandboxie-plusAGENTS.md

Sandboxie

sandboxie-plus/Sandboxie/AGENTS.md

change guidelines - Treat `Sandboxie/core` with extreme caution: bugs can cause BSODs or sandbox-escape security holes. Prefer minimal, surgical patches there over refactors. - Verify builds, branches, and properties

agent0aiAGENTS.md

agent-zero / agents

agent0ai/agent-zero/agents/AGENTS.md

metadata and inherited prompt specifics. | | [developer/AGENTS.md](developer/AGENTS.md) | Software development specialist profile. | | [hacker/AGENTS.md](hacker/AGENTS.md) | Cyber security and penetration testing specialist profile. | | [researcher/AGENTS.md](researcher/AGENTS.md) | Research, data analysis, and reporting specialist profile. | | [tiny

No other project uses it yet

agent0aiReads credentialsAGENTS.md

agent-zero

agent0ai/agent-zero/AGENTS.md

variables before plugin setup. - LiteLLM and OpenAI pins must remain compatible. Retain shared dependency security floors and verify upgrades with installed-SDK HTTP tests in `tests/test_litellm_sdk.py` using the framework runtime

No other project uses it yet

agent0aiAGENTS.md

agent-zero / api

agent0ai/agent-zero/api/AGENTS.md

changing handler behavior. - For auth, CSRF, upload/download, tunnel, or file endpoints, run the nearest security regression tests. - Check file-level documentation coverage with a script or shell loop that verifies

No other project uses it yet

agent0aiAGENTS.md

agent-zero / extensions

agent0ai/agent-zero/extensions/AGENTS.md

repeatedly when the lifecycle point can fire multiple times. - Secret masking, auth, security, and persistence extensions must not be bypassed by convenience changes. ## Work Guidance - Keep extension code small

No other project uses it yet

agent0aiAGENTS.md

agent-zero / helpers

agent0ai/agent-zero/helpers/AGENTS.md

belong in `api/`, tool behavior in `tools/`, and plugin-local logic inside plugin directories. - Security, auth, settings, file access, plugin discovery, extension dispatch, notifications, state snapshots, scheduler, tunnel, and WebSocket

No other project uses it yet

agent0aiAGENTS.md

agent-zero / plugins

agent0ai/agent-zero/plugins/AGENTS.md

update flows from ZIP, Git, and Plugin Index. | | [_plugin_scan/AGENTS.md](_plugin_scan/AGENTS.md) | LLM-guided security scanner for third-party plugins. | | [_plugin_validator/AGENTS.md](_plugin_validator/AGENTS.md) | Plugin manifest, structure, convention, and security

No other project uses it yet

agent0aiAGENTS.md

agent-zero / references

agent0ai/agent-zero/skills/a0-create-plugin/references/AGENTS.md

handlers. - Keep local-only work separate from community publication and catalog discovery separate from security scanning. - Preserve authentication, scope, user authorization, and unrelated runtime state. ## Work Guidance - Prefer existing framework

No other project uses it yet

agent0aiAGENTS.md

agent-zero / a0-manage-plugin

agent0ai/agent-zero/skills/a0-manage-plugin/AGENTS.md

behavior, scan expectations, and activation semantics current. - Distinguish Index discovery from model-based security scans and installation; metadata is not verified capability or safety. - Handle missing/null Index fields and check

agent0aiAGENTS.md

agent-zero / references

agent0ai/agent-zero/skills/a0-manage-plugin/references/AGENTS.md

handlers. - Keep local-only work separate from community publication and catalog discovery separate from security scanning. - Preserve authentication, scope, user authorization, and unrelated runtime state. ## Work Guidance - Prefer existing framework

No other project uses it yet

agent0aiAGENTS.md

agent-zero / tests

agent0ai/agent-zero/tests/AGENTS.md

Tests DOX ## Purpose - Own pytest regression, security, integration, and contract tests. - Keep tests focused on behavior that should remain stable across framework changes. ## Ownership - Test files live directly under `tests

No other project uses it yet

elizaOSAGENTS.md

eliza

elizaOS/eliza/AGENTS.md

desktop/mobile inspection. - Submit changes through a PR against `develop`. Report vulnerabilities privately through GitHub Security Advisories. The community plugin registry is retired; first-party catalog data lives in `packages/core/src/catalog/`. Getting

No other project uses it yet