Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/openai/openai-agents-python/agents-mdgit clone --depth 1 https://github.com/openai/openai-agents-pythonWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.08006 | $0.08006 |
| Opus 5 | $0.04003 | $0.04003 |
| Sonnet 5 | $0.01601 | $0.01601 |
| Haiku 4.5 | $0.00801 | $0.00801 |
Grade A, and why
openai-agents-python AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributor Guide
This guide helps new contributors get started with the OpenAI Agents Python repository. It covers repo structure, how to test your work, available utilities, and guidelines for commits and PRs.
Location: AGENTS.md at the repository root.
Table of Contents
Policies & Mandatory Rules
Mandatory Skill Usage
Repository skills are stored under .agents/skills/. A reference such as $<skill-name> in this file is a repository instruction reference, not a request for manual user invocation. When a rule requires a skill, read .agents/skills/<skill-name>/SKILL.md completely before taking task actions, follow its instructions, and resolve referenced files relative to that skill directory.
$code-change-verification
Run $code-change-verification before marking work complete when changes affect runtime code, tests, or build/test behavior.
Run it when you change:
src/agents/(library code) or shared utilities.tests/or add or modify snapshot tests.examples/.- Build or test configuration such as
pyproject.toml,Makefile,mkdocs.yml,docs/scripts/, or CI workflows.
You can skip $code-change-verification for docs-only or repo-meta changes (for example, docs/, .agents/, README.md, AGENTS.md, .github/), unless a user explicitly asks to run the full verification stack.
Treat $code-change-verification as the post-review final gate, not as an iterative review check. When $implementation-final-review applies, satisfy its clean-review condition before starting the repository-wide format, lint, typecheck, and test stack. Immediately before starting that stack, use available read-only task or process evidence to check for another broad test, typecheck, build, examples, or integration command already running on the same host. When concrete contention is visible, keep making progress on review, remediation, evidence preparation, or focused checks and defer the broad stack until capacity is available. Do not add a repository lock, host-wide mutex, sentinel file, or user-triggered finalize step. Lack of host telemetry alone is not a blocker.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 330 lines · 8,006 tokens per session scan A 337fbeca5f88
openai-agents-python AGENTS.md is an instructions file published in the GitHub repository openai/openai-agents-python (29,075 stars, last pushed 4d ago), licensed MIT. It adds 8,006 tokens to every session, about $0.0400 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
instructor CLAUDE.md
Instructions for 567-labs/instructor, covering claude.md, instructor development guide, commands, installation & setup and code style guidelines.
E2B CLAUDE.md
Instructions for e2b-dev/E2B: Use pnpm for node and uv for python to install and update dependencies. Run pnpm run format, pnpm run lint and pnpm run typecheck before committing changes. When modifying the SDK packages, ensure equivalent changes are applied to both JS as well as sync and async Python implementations.…
cocoindex-code CLAUDE.md
Instructions for cocoindex-io/cocoindex-code, covering claude.md, build and test commands, architecture, process model and key layers.
AutoGPT AGENTS.md
AGENTS.md instructions for Significant-Gravitas/AutoGPT, covering autogpt platform contribution guide, directory overview, code style, frontend guidelines and testing.
AI-Gateway AGENTS.md
Instructions for Azure-Samples/AI-Gateway, covering agents.md, directory structure, labs/, modules/ and shared/.
opengeni AGENTS.md
Instructions for Cloudgeni-ai/opengeni, covering agent / automation notes (opengeni), full local stack, architecture notes, pull-request delivery across moving main and keeping these notes current.