qwik
QwikDev/qwik/AGENTS.md
unit.ts(x)` | Vitest unit files | | `*.spec.ts(x)` | Vitest spec files | | `*.e2e.ts` | Playwright e2e files | ### Security And Supply Chain Treat security-sensitive changes as behavior changes even when they look like
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.
QwikDev/qwik/AGENTS.md
unit.ts(x)` | Vitest unit files | | `*.spec.ts(x)` | Vitest spec files | | `*.e2e.ts` | Playwright e2e files | ### Security And Supply Chain Treat security-sensitive changes as behavior changes even when they look like
QwikDev/qwik/.ruler/AGENTS.md
unit.ts(x)` | Vitest unit files | | `*.spec.ts(x)` | Vitest spec files | | `*.e2e.ts` | Playwright e2e files | ### Security And Supply Chain Treat security-sensitive changes as behavior changes even when they look like
matomo-org/matomo/AGENTS.md
range review | `matomo-review` | | In-development debt or maintainability review | `matomo-debt-check` | | Security-sensitive changes: access control, CSRF, SQL, request parsing, tokens, secrets | `matomo-security-rules` | | Public API methods
NirDiamant/agents-towards-production/AGENTS.md
independent tutorial tracks, each covering one layer of the production stack: orchestration, memory, retrieval, security and guardrails, observability and tracing, evaluation, deployment, GPU serving, fine-tuning and user interfaces
netbox-community/netbox/AGENTS.md
ruff) and the full test suite across the supported Python version matrix. - **`codeql.yml`** — CodeQL security scanning. - **`claude.yml`** — Claude Code automation hook; triggers on issue/PR comments mentioning `@claude`. - **`claude-issue-triage.yml`** — Automated issue
oracle/graal/AGENTS.md
included when behavior changes. - [ ] Flag and ask for extra permission for changes related to security (e.g., touching cryptographic code
NVIDIA/OpenShell/AGENTS.md
OCSF builder + `ocsf_emit!()` for events that represent **observable sandbox behavior** visible to operators, security teams, or agents monitoring the sandbox: - Network decisions (allow, deny, bypass detection) - HTTP/L7 enforcement decisions
Steady10 mentions in 2 weeks
No other project uses it yet
containerd/containerd/AGENTS.md
docs/garbage-collection.md) | | Namespace propagation through context | [Namespaces](docs/namespaces.md) | | Daemon-side image transfers | [Transfer service](docs/transfer.md) | ## Security findings Before scanning for security issues, evaluating a suspected vulnerability, or drafting a security report
github/docs/content/copilot/responsible-use/agents.md
assigned issues. The cloud agent runs in an ephemeral, firewalled environment with automated security scanning. * **Copilot Cloud**: Copilot in the Cloud (GitHub Copilot on GitHub.com, GitHub Mobile, or anywhere that
xbmc/xbmc/AGENTS.md
issues that should block the change. * Report only regressions, correctness problems, build failures, security issues, or behavior that contradicts the stated intent. * Do not suggest optional improvements, cleanup, alternative wording
vulhub/vulhub/AGENTS.md
Guide Vulhub is an open-source collection of pre-built vulnerable Docker environments for security education. ## Project Structure ``` base/ / /Dockerfile # Base Docker images for vulnerable software / / # Vulnerability environments ├── docker-compose.yml ├── README.md
Steady16 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Steady21 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
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.