extra: Instructions file for Codex

AGENTS.md

extra AGENTS.md is an instructions file for Codex, OpenCode from extra-org/extra. It costs 4,051 tokens per session, scanned A, original, MIT.

Repository instructions for AI coding agents working on extra-org/extra. They describe the project's purpose, architecture, rules, folder structure, commands, and other expectations for making changes.

In plain words
What is it for?
Use it when an AI agent needs to understand, validate, generate, run, serve, or modify this YAML-based platform for building AI agent systems.
Why use it?
They give an agent the project context it needs before editing code. This reduces the risk of changes that conflict with the repository's design or development process.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

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

Reuse

Borrowing it

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

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 extra AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/extra-org/extra/agents-md"><img src="https://agentmods.dev/badge/instructions/extra-org/extra/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,051 This file is loaded in full into every session.
When invoked 4,051 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.04051 $0.04051
Opus 5.5 $0.01620 $0.01620
Sonnet 5.5 $0.00810 $0.00810
Haiku 4.5 $0.00405 $0.00405

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

Security

Grade A, and why

extra 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 11d 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 · 359 lines

How it starts

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

AGENTS.md

This file is the operating manual for every AI coding agent working in this repository. Read it fully before making any change. If a task ever conflicts with this file, this file wins — stop and ask for clarification.


1. Project mission

This repository is a declarative platform for building AI agent systems.

Developers describe an agent system in YAML. The platform validates that YAML, compiles it into a typed internal graph, and runs it through a long-lived runtime that renders prompt files, calls resolver/tool plugins and MCP servers, exposes an API, and produces execution traces.

The repository is in active development. The YAML validator, compiler, runtime engine (orchestrators run as supervisor agents), resolver plugin system, tool plugin loading, MCP client (local and remote servers, including authenticated MCP via hooks), the runtime hooks system (11 lifecycle points — see docs/RUNTIME_HOOKS.md), per-run execution-limit guardrails (see docs/EXECUTION_LIMITS.md), prompt rendering, and the CLI (validate, inspect, generate, run, serve, chat) are implemented. Model access supports both Anthropic and Amazon Bedrock. Two HTTP API layers exist: a thin agent_engine API (/invoke, /stream), started by agentctl serve (default port 8090) — stateless, no persistence, no web client — and agent_manager — a conversation lifecycle service built on top of it with process-local storage by default, opt-in SQLite/Postgres persistence, SSE streaming, and the official React web client, started by the separate agent-manager console script (default port 8100). agentctl chat is a separate, ephemeral developer console that persists nothing (see docs/ARCHITECTURE.md §14 for detail). Basic observability (structured logging plus a Langfuse callback provider) is wired in. A Dockerfile/entrypoint.sh provide a basic container image.

The access plugin is wired into child filtering, but the request-context gate that should populate real identity/permissions into it is not yet implemented — access filtering currently runs against an empty context, so protected nodes are not actually enforced today. Treat this as an open security gap, not a finished feature. See docs/ROADMAP.md for per-phase status. Agents implement the product task-by-task using the files in tasks/, though the package layout has evolved beyond what the original numbered tasks describe (see §4).

Read the full file on GitHub · 359 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. 11d ago Changed · +1 lines · +23 tokens per session 18598cbca5d4
  2. 2mo ago First seen · 358 lines · 4,028 tokens per session scan A 989ae47478a4

Subscribe to this mod's changes

extra AGENTS.md is an instructions file published in the GitHub repository extra-org/extra (117 stars, last pushed 5d ago), licensed MIT. It adds 4,051 tokens to every session, about $0.0162 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

runtm copilot-instructions.md

Copilot instructions for runtm-ai/runtm, covering runtm tool instructions, critical rules, structure, adding endpoints and app/api/v1/myendpoint.py.

runtm-ai/runtm · 297 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens