openpi: Instructions file for Codex

AGENTS.md

openpi AGENTS.md is an instructions file for Codex, OpenCode from openpi-dev/openpi. It costs 1,541 tokens per session, scanned A, original, MIT.

A set of instructions for developing OpenPI, a capability layer that extends the Pi coding agent without replacing its core system.

In plain words
What is it for?
Use it when designing OpenPI features, preserving Pi's lifecycle and terminology, or defining permissions, limits, isolation, and delegation boundaries.
Why use it?
It clarifies which decisions belong to the model and which rules belong to the runtime, helping prevent unclear ownership and unnecessary framework layers.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents.

This is openpi-dev/openpi's own configuration. It tells Codex and OpenCode how to work on openpi itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openpi configures →

Reuse

Borrowing it

Nothing to install: this file belongs to openpi-dev/openpi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/openpi-dev/openpi/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/openpi-dev/openpi

Made for: Codex, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for openpi AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/openpi-dev/openpi/agents-md/github.svg)](https://agentmods.dev/instructions/openpi-dev/openpi/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/openpi-dev/openpi/agents-md"><img src="https://agentmods.dev/badge/instructions/openpi-dev/openpi/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for openpi AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/openpi-dev/openpi/agents-md"><img src="https://agentmods.dev/badge/instructions/openpi-dev/openpi/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,541 This file is loaded in full into every session.
When invoked 1,541 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01541 $0.01541
Opus 5.5 $0.00616 $0.00616
Sonnet 5.5 $0.00308 $0.00308
Haiku 4.5 $0.00154 $0.00154

Measured 9d ago against content hash 84c3778cfbc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

openpi 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 9d ago.

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.

AGENTS.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenPI agent contract

OpenPI is a Pi-native capability layer, not a second agent operating system. Extend Pi at its existing seams and preserve its lifecycle, vocabulary, and sources of truth.

Design stance

Build for model leverage

  • Prefer capabilities whose usefulness increases as models improve.
  • Give the model small, orthogonal mechanisms and high-fidelity feedback. Let the model decide strategy, decomposition, delegation, and synthesis.
  • Encode safety and execution invariants in the runtime. Do not encode a preferred reasoning process, keyword router, or fixed orchestration workflow unless correctness requires it.
  • Before adding a framework abstraction, ask whether a stronger model could use the underlying Pi primitive directly. If yes, expose or strengthen that primitive instead.

Keep ownership clear

The model owns judgment:

  • understanding intent and choosing an approach;
  • deciding whether and how to delegate;
  • adapting to evidence and synthesizing results;
  • deciding when user input is needed.

The runtime owns enforceable facts:

  • permissions, trust, isolation, and capability boundaries;
  • concurrency, call, time, and resource limits;
  • lifecycle, cancellation, cleanup, persistence, and recovery;
  • atomicity, idempotency, replay safety, and fail-closed outcomes;
  • observable execution state and exact terminal evidence.

Do not rely on prompts for runtime invariants. Do not move model judgment into a rigid state machine merely because it is easier to test.

Preserve Pi-native composition

  • Pi remains the source of truth for Sessions, provider/model selection, Skills, project Trust, and ordinary tools.
  • Reuse Pi events, messages, tools, extension hooks, and session lifecycle before introducing parallel storage or control planes.
  • Keep model-facing schemas compact and progressively disclose specialized capabilities and detailed instructions only when needed.
  • Treat canonical execution facts, model-visible context, and operator-facing UI as distinct projections. Never infer completion from labels or presentation state.
  • Prefer one general composable capability over several workflow-specific commands.

Read the full file on GitHub · 90 lines

Changes

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.

  1. 9d ago Changed · +58 tokens per session 84c3778cfbc8
  2. 11d ago Changed · +1 lines · +19 tokens per session e1efca472c96
  3. 13d ago Changed · +36 tokens per session a6bd4d42f94b
  4. 27d ago Changed · +41 tokens per session c89f5560e10f
  5. 1mo ago First seen · 89 lines · 1,387 tokens per session scan A 66bc8e442646

Subscribe to this mod's changes

openpi AGENTS.md is an instructions file published in the GitHub repository openpi-dev/openpi (196 stars, last pushed 4d ago), licensed MIT. It adds 1,541 tokens to every session, about $0.0062 per session on Opus 5.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.

Related

Other instructions, from other repositories