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/eep-dev/eep/agents-mdgit clone --depth 1 https://github.com/eep-dev/EEPWhat 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.01215 | $0.01215 |
| Opus 5 | $0.00607 | $0.00607 |
| Sonnet 5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
EEP 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — How coding agents work with this repository
Entity Engagement Protocol (EEP) — open standard for push-based, verifiable communication between digital entities and subscribers (including AI agents). This file is the fast path for autonomous tools (Claude Code, Cursor, Cline, OpenClaw, etc.). Read this first, then llms.txt or llms-full.txt for depth.
What to know in 30 seconds
- Not a replacement for MCP (tools), A2A (agent↔agent), or ANP. EEP is entity engagement: discovery, SSE/webhooks, optional WebSockets, gates (identity, payment, agreements, …), signed deliveries. See README.md positioning table.
- Normative truth: docs/current/SPECIFICATION.md + schemas/v0.1/.
- Webhook signatures (outbound POST to subscribers): Standard Webhooks-style headers
webhook-id,webhook-timestamp,webhook-signature(see spec §5). Do not invent a separateX-EEP-Signaturefor webhook bodies.
Repository map
| Need | Location |
|---|---|
| Full spec | docs/current/SPECIFICATION.md |
| JSON Schemas | schemas/v0.1/ |
| TypeScript packages | packages/@eep-dev/* |
| Python ports | packages/eep-*-python/ |
| Conformance against a live URL | packages/@eep-dev/compliance-cli |
| Scaffold + generated artifacts | packages/@eep-dev/setup-cli (eep-setup) |
| HTTP adapters (Express, Fastify, Hono, Koa, FastAPI, …) | packages/@eep-dev/middleware, packages/eep-middleware-python |
| MCP ↔ EEP HTTP bridge | packages/@eep-dev/mcp-bridge |
| One-shot adopt flow for an app repo | packages/@eep-dev/agent-adopt |
| Agent strategy / launch notes | docs/strategy/ |
| LangGraph example | examples/langgraph-eep-agent/ |
| Docker reference stack | examples/eep-reference-implementation/ |
Adopt EEP into another project (typical agent task)
From the target application repository (not necessarily this monorepo):
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 · 95 lines · 1,215 tokens per session scan A b3626b3cf3c1
EEP AGENTS.md is an instructions file published in the GitHub repository eep-dev/EEP (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,215 tokens to every session, about $0.0061 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
harness-sdk AGENTS.md
AGENTS.md instructions for strands-agents/harness-sdk, covering agent development guide - strands agents monorepo, context, monorepo layout, where the "why" lives: team/ and writing code.
wanaku CLAUDE.md
Instructions for wanaku-ai/wanaku, covering wanaku, core guidelines, quick start, build info and architecture.
autogen copilot-instructions.md
Copilot instructions for microsoft/autogen, covering autogen multi-agent ai framework, working effectively, prerequisites and environment setup, python development workflow and quick validation (under 1 second each).
hatch3r CLAUDE.md
Instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).
cybara CLAUDE.md
Instructions for metaspartan/cybara, covering ai coding rules for cybara agent platform, no code comments (strict), runtime environment, import rules and ✅ do.
cybara AGENTS.md
Instructions for metaspartan/cybara, covering cybara agent rules, package manager policy (strict), command translation, typescript type safety and no comments.