vitess / changelog
vitessio/vitess/changelog/AGENTS.md
fixes, such as stricter validation that rejects input Vitess used to accept - Security fixes that have a published advisory. Until the advisory is public, leave
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
vitessio/vitess/changelog/AGENTS.md
fixes, such as stricter validation that rejects input Vitess used to accept - Security fixes that have a published advisory. Until the advisory is public, leave
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
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
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
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
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
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
Steady22 mentions in 2 weeks
No other project uses it yet
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
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-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
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.