pydantic-ai-gepa: Instructions file for Codex

AGENTS.md

pydantic-ai-gepa AGENTS.md is an instructions file for Codex, OpenCode from indexedlabs/pydantic-ai-gepa. It costs 928 tokens per session, scanned A, original, MIT.

Repository guidance for pydantic-ai-gepa, a Python project that optimizes AI-agent prompts and components.

In plain words
What is it for?
Use it to orient development, install dependencies with uv, run tests, and organize new code.
Why use it?
It records where code, examples, tests, dependencies, and workflow information belong, reducing uncertainty during changes.

Instructions file for CodexOpenCode

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

This is indexedlabs/pydantic-ai-gepa's own configuration. It tells Codex and OpenCode how to work on pydantic-ai-gepa 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 pydantic-ai-gepa configures →

Reuse

Borrowing it

Nothing to install: this file belongs to indexedlabs/pydantic-ai-gepa. 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/indexedlabs/pydantic-ai-gepa/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/indexedlabs/pydantic-ai-gepa

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 pydantic-ai-gepa AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/indexedlabs/pydantic-ai-gepa/agents-md/github.svg)](https://agentmods.dev/instructions/indexedlabs/pydantic-ai-gepa/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/indexedlabs/pydantic-ai-gepa/agents-md"><img src="https://agentmods.dev/badge/instructions/indexedlabs/pydantic-ai-gepa/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 pydantic-ai-gepa AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/indexedlabs/pydantic-ai-gepa/agents-md"><img src="https://agentmods.dev/badge/instructions/indexedlabs/pydantic-ai-gepa/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 928 This file is loaded in full into every session.
When invoked 928 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.00928 $0.00928
Opus 5.5 $0.00371 $0.00371
Sonnet 5.5 $0.00186 $0.00186
Haiku 4.5 $0.00093 $0.00093

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

Security

Grade A, and why

pydantic-ai-gepa 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 12d 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 · 38 lines

How it starts

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

Repository Guidelines

Specs and tasks

  • Specs and decisions for this library live in the Mighty Next graph, not in this repository. Before changing behavior, find the pages that own the code you are about to touch with mighty invoke mighty.graph/governing --json '{"paths":["<repo-relative path>"]}', or browse the subtree starting at specs/pydantic-ai-gepa/overview.md. Tasks live in Linear (Indexed Labs); the orchestrator that dispatched you owns both.
  • The v1 records under .mighty/ (such as .mighty/loro/ and .mighty/config.json) are a read-only historical record; do not write to them (mt is no longer installed for this repo). .mighty/checks/ is active configuration for the hosted review checks and is edited like any other file.

Project Structure & Module Organization

  • Core library lives in src/pydantic_ai_gepa/, organized by responsibility (runner.py exposes the high-level optimization API, components.py handles candidate transforms, cache.py manages GEPA caching, etc.).
  • Example agents and walkthrough scripts sit in examples/, and experimental runs land in optimization_results/ for posterity.
  • Tests reside in tests/ with fixtures in tests/conftest.py; favor mirroring module names (test_signature_agent.py, test_cache.py).
  • Packaging metadata is defined in pyproject.toml; the repo uses the uv workflow (uv.lock) instead of ad‑hoc virtualenvs.

Build, Test, and Development Commands

  • uv sync --all-extras installs the project plus dev dependencies listed under [dependency-groups.dev].
  • uv run pytest executes the full test suite; add -k pattern to focus on a module (uv run pytest -k signature).
  • uv run python examples/classification.py runs the end-to-end GEPA prompt optimization example; prefer uv run so dependencies resolve consistently.

Coding Style & Naming Conventions

  • Follow PEP 8 with 4-space indents and snake_case for functions, module-level symbols, and filenames; keep classes in PascalCase.
  • Preserve the existing type-hinted style—public APIs pass strongly-typed sequences (e.g., Sequence[Case[InputT, OutputT, MetadataT]]) and explicit Model | KnownModelName unions.
  • Module docstrings summarize purpose; add short comments only where control flow is non-obvious (see runner.py contextmanagers for tone).

Read the full file on GitHub · 38 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. 12d ago Changed · +33 tokens per session 619610263011
  2. 14d ago Changed · +6 lines · +233 tokens per session acd9d463239c
  3. 1mo ago Changed · -1 lines · +26 tokens per session 069f7bf14240
  4. 1mo ago First seen · 33 lines · 636 tokens per session scan A fb9582ac1354

Subscribe to this mod's changes

pydantic-ai-gepa AGENTS.md is an instructions file published in the GitHub repository indexedlabs/pydantic-ai-gepa (36 stars, last pushed 13d ago), licensed MIT. It adds 928 tokens to every session, about $0.0037 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-09-01.

Related

Other instructions, from other repositories