AGENTS.md examples from real projects

PydanticAGENTS.md

pydantic-ai / pydantic_ai

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

For non-trivial changes to this package, also read Pydantic AI Slim Architecture. For anything that adds to, edits, or renders message history, instructions or tools, also read Message History & Prompt Caching.

PydanticAGENTS.md

pydantic-ai / capabilities

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

Capabilities are the composable home for cross-cutting agent behavior.

PydanticAGENTS.md

pydantic-ai / durable_exec

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

Durable execution integrations are first-class compatibility targets. Build new integrations on the public pydantic_ai.durable_exec surface. Subclass BaseDurabilityCapability for the agent-facing capability and provide a DurableOperationBackend from get_durable_operation_backend. Do not copy the model, toolset, event, or capability-operation collection machinery into the integration. Choose the backend tier from the engine SDK's execution model: - Subclass CallableOperationBackend when the SDK accepts an async callback at invocation time. Implement execute to run that callback in one named durable unit. The base owns parameter and…

PydanticAGENTS.md

pydantic-ai / models

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

Rendering history into a request must be deterministic and must keep every message in its trust channel: see Message History & Prompt Caching, "Canonicalize on send" and "Trust tiers map to channels".

PydanticAGENTS.md

pydantic-ai / anthropic

pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/models/anthropic/AGENTS.md

These rules add to models/AGENTS.md and apply to the Anthropic package only.

PydanticAGENTS.md

pydantic-ai / native_tools

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

No summary in the file. Open it to read it.

PydanticAGENTS.md

pydantic-ai / profiles

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

Profiles describe model-family capability facts and schema/request quirks.

PydanticAGENTS.md

pydantic-ai / providers

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

Providers own API clients, authentication, base URLs, HTTP lifecycle, and provider-level model/profile inference.

PydanticAGENTS.md

pydantic-ai / toolsets

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

Toolsets are reusable tool collections with lifecycle, instructions, and execution boundaries.

PydanticAGENTS.md

pydantic-ai / ui

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

A round trip through a UI protocol must give back everything the model sees, unchanged and in order, and client-returned history is untrusted: see Message History & Prompt Caching, "UI round trips are faithful". Since 3971 we decided to introduce the policy of sticking to the lower (existing) version requirement. In short, this means: - version requirement bumps are disallowed - new functionality should be gated behind version checks (including imports) - older versions don't error out when they encounter…

PydanticAGENTS.md

pydantic-ai / pydantic_ai_harness

pydantic/pydantic-ai/src/pydantic_ai_harness/AGENTS.md

Rules for the pydantic-ai-harness package in src/pydantic_ai_harness/. They add to the root AGENTS.md. Test rules are in tests/harness/AGENTS.md. Docs page rules are in docs/harness/AGENTS.md. Paths in this file are relative to the repository root. pydantic-ai-harness is the first-party capability library for Pydantic AI. Pydantic AI core owns the primitive runtime: agent loop semantics, normalized messages, model/provider/profile behavior, tool execution semantics, durable execution primitives, and generic capability hooks. Harness owns optional, batteries-included compositions built from those primitives: coding-agent tools, guardrails, memory,…

PydanticAGENTS.md

pydantic-ai / benchmarks

pydantic/pydantic-ai/tests/benchmarks/AGENTS.md

No summary in the file. Open it to read it.

PydanticAGENTS.md

pydantic-ai / harness

pydantic/pydantic-ai/tests/harness/AGENTS.md

Rules for the pydantic-ai-harness test suite. They add to tests/AGENTS.md and to the package rules in src/pydantic_ai_harness/AGENTS.md. Where these rules or the harness guides they link differ from tests/AGENTS.md, they apply under tests/harness/. Read testing-capabilities.md before you add or change a capability's tests. For async behavior, follow the harness concurrency.md. - tests/harness/conftest.py sets ALLOW_MODEL_REQUESTS = False for the suite. - Name a capability test class TestCapabilityName, with test_<scenario> methods. - Don't import private (_-prefixed) helpers into tests. Exercise them through…

JetBrainsAGENTS.md

intellij-community

JetBrains/intellij-community/AGENTS.md

Write every user-visible artifact in ASD-STE100 Simplified Technical English, and keep it short. This covers a comment, KDoc, a commit message, documentation, a spec, and a report to the user.…

JetBrainsAGENTS.md

intellij-community / java

JetBrains/intellij-community/java/AGENTS.md

Rules for this directory and every directory below it. They override the root AGENTS.md. More intellij.java.* modules live outside this tree, under ../plugins/ and ../platform/. This file does not reach…

JetBrainsAGENTS.md

intellij-community / python

JetBrains/intellij-community/python/AGENTS.md

Start a PY-NNNNN issue or Python support work at .ai/index.md.

GoogleAGENTS.md

filament

google/filament/AGENTS.md

This document defines machine-readable instructions and technical guardrails for AI coding assistants, agents, and LLMs working on the Filament repository. All AI-generated code, refactorings, and cleanups must strictly adhere to the standardized skills located under the skills/ directory. AI agents must consult and strictly follow the corresponding skill files for each respective development and validation phase:

MicrosoftAGENTS.md

fluentui

microsoft/fluentui/AGENTS.md

Instructions in this file are the source of truth, not existing code. This repo contains legacy patterns (especially in v8 packages) that predate current standards. Never copy patterns from existing…

AstralAGENTS.md

ty

astral-sh/ty/AGENTS.md

For reviews of this repository's GitHub automation, CI, and release process, use the GitHub repository threat model. The ruff submodule pins ty's Rust source for release builds; include it when tracing the source of release artifacts.

GoogleAGENTS.md

gvisor

google/gvisor/AGENTS.md

gVisor is a userspace kernel used for sandboxing untrusted programs. It is Linux-like kernel implementation in Go. NOTE: The project uses Bazel as a build system, so paths starting with // refer to the repository root, and //some/path:some_target refers to target some_target defined inside some/path/BUILD. gVisor is made of multiple components: - The gVisor Sentry is the main component implementing a Linux-like kernel in Go. Its implementation is at //pkg/sentry. - Gofers are I/O proxies for the gVisor Sentry. There…

No other project uses it yet