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 skills add eep-dev/EEP --skill claude-code-skillgit clone --depth 1 https://github.com/eep-dev/EEPWrote 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.
[](https://agentmods.dev/skills/eep-dev/eep/claude-code-skill)<a href="https://agentmods.dev/skills/eep-dev/eep/claude-code-skill"><img src="https://agentmods.dev/badge/skills/eep-dev/eep/claude-code-skill/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.
<a href="https://agentmods.dev/skills/eep-dev/eep/claude-code-skill"><img src="https://agentmods.dev/badge/skills/eep-dev/eep/claude-code-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 21 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 29 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.00453 |
| Opus 5.5 | $0.00025 | $0.00181 |
| Sonnet 5.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 1mo 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.
- 1mo 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 today), licensed Apache-2.0. It adds 63 tokens to every session and 453 once invoked, about $0.0003 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.
Other skills, from other repositories
api-debug
Debug REST, GraphQL, webhook, and OAuth/API-key integrations with layered request, auth, schema, and response checks.
agentproto-llm-endpoint
Use the local LLM endpoint proxy (localhost:18090) — or your own gated public deployment — to route Claude Code / Claude SDK through custom providers (OpenRouter, Moonshot, Groq, ZAI) via an Anthropic-compatible gateway. Covers adapter-specific behaviors, auth patterns, proxy codenames, and common failure modes.
game-networking
Design, implement, test, secure, and profile multiplayer game networking across engines, including authority, replication, prediction, rollback, lobbies, reconnects, and adverse network conditions.
hatch3r-api-spec
Generates and validates OpenAPI specifications from codebase. Covers endpoint design, schema validation, and documentation generation.
hatch3r-scalability-verify
Scalability verification gate before commit/release — stateless-handler ratio, back-pressure patterns, idempotency-key adoption, queue-based offloading, pool sizing, bulkheads, load-test pass at target scale.
hatch3r-cli-jq
JSON processor and query language. Use when shaping JSON streams via jq-syntax filters and select expressions; invoke jq. Reads stdin and emits stdout; integrates seamlessly into shell pipelines.