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 skills/eep-dev/eep/claude-code-skillnpx skills add eep-dev/EEP --skill claude-code-skillgit 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.00063 | $0.00453 |
| Opus 5 | $0.00032 | $0.00227 |
| Sonnet 5 | $0.00013 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
eep-adopt-app 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 2d 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.
What it actually says
Adopt EEP in an app repository
When this triggers: They ask to add EEP, entity streams, or run agent-adopt on a codebase.
Not in scope here: SEO/GEO promises, "ranking" claims, or replacing MCP. See references/positioning.md if they blur EEP and MCP.
Flow
-
Work in the application root (the service they want to expose), not the EEP spec repo unless they are developing EEP itself.
-
Run:
npx @eep-dev/agent-adopt --project . --no-compliance -
Read
EEP_ADOPTION_REPORT.mdandeep-generated/. Ifverifyfailed, fixapply/ config and re-run; see AGENTS.md on the EEP repo for flags. -
If they have a public base URL and credentials:
npx @eep-dev/agent-adopt --project . \ --compliance-target "$URL" \ --compliance-api-key "$KEY" \ --compliance-entity u/entity -
Wire the server: integrate-eep-after-setup-cli. Node:
@eep-dev/middleware+@eep-dev/gates. Python:eep-middleware-python. Generated wiring files, if any, are hints—still need review for production. -
For exposing MCP and EEP in one place, see
@eep-dev/mcp-bridgein the EEP monorepo (references/positioning.md).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 38 lines · 63 tokens per session scan A ef82e3b11108
eep-adopt-app is a skill published in the GitHub repository eep-dev/EEP (22 stars, last pushed 2d ago), licensed Apache-2.0. It adds 63 tokens to every session and 453 once invoked, about $0.0003 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 skills, from other repositories
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
pr-create
Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub.
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).