e2a: Instructions file for Codex

AGENTS.md

e2a AGENTS.md is an instructions file for Codex, OpenCode from tokencanopy/e2a. It costs 7,115 tokens per session, scanned A, original, Apache-2.0.

Project instructions for e2a, a service whose public repository must not contain customer or production-derived data. They define the repository layout, documentation sources, and development rules.

In plain words
What is it for?
Use them when changing, testing, documenting, or reviewing this public repository. They are especially relevant when handling customer identifiers, messages, URLs, timestamps, or generated output.
Why use it?
They make the boundary between safe public examples and private customer information explicit. This helps prevent accidental disclosure in code, tests, issues, logs, screenshots, or commits.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tokencanopy/e2a/agents-md"><img src="https://agentmods.dev/badge/instructions/tokencanopy/e2a/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7,115 This file is loaded in full into every session.
When invoked 7,115 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.07115 $0.07115
Opus 5.5 $0.02846 $0.02846
Sonnet 5.5 $0.01423 $0.01423
Haiku 4.5 $0.00711 $0.00711

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

Security

Grade A, and why

e2a 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 18d 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 · 466 lines

How it starts

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

AGENTS.md

Guidance for AI coding agents working in this repository (Claude Code reads this file via the @AGENTS.md import in CLAUDE.md). Assumes no prior knowledge of the project. For deeper prose, see README.md (product), CONTRIBUTING.md (contributor workflow), docs/ (API reference, deployment, design docs), and SECURITY.md.

Public repository data boundary (non-negotiable)

This repository and all of its GitHub surfaces are public. Never put real customer data or non-public production-derived data in source files, tests, fixtures, generated artifacts, commit messages, branch names, PR/issue/discussion titles or bodies, review comments, screenshots, log excerpts, or benchmark output. This includes email and agent addresses, customer domains or names, user/account/agent/message/contact IDs, message content or subjects, customer-specific URLs or IP addresses, timestamps tied to customer activity, and delivery, bounce, or incident details that can be correlated to a customer. An address on agents.e2a.dev is a customer identifier, not a safe example value. Public service metadata deliberately documented for users, such as https://api.e2a.dev, is not customer data.

Before any GitHub-facing write, replace production-derived values with synthetic ones such as example.com, .test, .invalid, agents.localhost, or clearly fictional resource IDs. Describe production evidence only in anonymized, non-correlatable terms (for example, "a production customer saw repeated SMTP rejections"). Keep exact evidence only in an approved private incident or operations system. Relevance to a fix is not an exception to this boundary.

If customer data is found before push, stop and rewrite the affected files and commits. If it reaches GitHub, treat it as a data exposure: stop propagation, notify Josh/security, sanitize the PR or issue, rewrite reachable Git history, check related refs/forks/caches, and contact GitHub Support when cached views or references need purging. Deleting the visible text alone is not sufficient.

Read the full file on GitHub · 466 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. 18d ago Changed · +1 lines · +20 tokens per session 9636ad7e4946
  2. 19d ago Changed · +3 lines · +46 tokens per session 9215c9faca4e
  3. 1mo ago Changed · +13 lines · +226 tokens per session ae417e54742d
  4. 1mo ago First seen · 449 lines · 6,823 tokens per session scan A d0e192467c73

Subscribe to this mod's changes

e2a AGENTS.md is an instructions file published in the GitHub repository tokencanopy/e2a (194 stars, last pushed 6d ago), licensed Apache-2.0. It adds 7,115 tokens to every session, about $0.0285 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

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,649 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,257 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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 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,731 tokens