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.
git 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/rules/eep-dev/eep/eep-agent-adopt)<a href="https://agentmods.dev/rules/eep-dev/eep/eep-agent-adopt"><img src="https://agentmods.dev/badge/rules/eep-dev/eep/eep-agent-adopt/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/rules/eep-dev/eep/eep-agent-adopt"><img src="https://agentmods.dev/badge/rules/eep-dev/eep/eep-agent-adopt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00391 |
| Opus 5.5 | $0.00000 | $0.00156 |
| Sonnet 5.5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
eep-agent-adopt 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
EEP in this repo (Cursor)
If they are in their app root (not the eep-dev/EEP clone), wire EEP with the published CLI. Normative background when needed: AGENTS.md in the EEP repo.
-
From the app root:
npx @eep-dev/agent-adopt --project . --no-compliance -
If they give a live API base URL (staging/production), you can add checks:
npx @eep-dev/agent-adopt --project . --compliance-target "https://…" --compliance-entity u/… -
After
eep-generated/looks good, add runtime deps: Node →@eep-dev/middlewareand@eep-dev/gates; Python →eep-middleware-python. Follow the EEP guide integrate-eep-after-setup-cli. The adopt tool may have droppedeep.express.wiring.tsoreep_fastapi_wiring.py—treat that as a starting point, not a full prod setup.
EEP is about pushes, signed deliveries, and gates. MCP is about invoking tools. Same stack can use both; EEP is not a drop-in for MCP and the other way around.
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 · 28 lines · 0 tokens per session scan A 9089e4808ff0
eep-agent-adopt is a cursor rule published in the GitHub repository eep-dev/EEP (22 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 391 tokens. 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 cursor rules, from other repositories
hatch3r-resilience-patterns
Resilience patterns in user code — circuit breakers, retry with decorrelated jitter, timeouts with deadline propagation, idempotency keys, bulkheads, hedged requests.
hatch3r-contract-testing
Consumer-driven and spec-driven contract testing between services — Pact, Schemathesis, Dredd, pact-broker can-i-deploy gate.
hatch3r-api-design
REST, GraphQL, and gRPC contract patterns covering versioning, auth, CORS, pagination, webhooks, rate limiting, and security headers.
hatch3r-auth-patterns
Authentication and authorization patterns for end-user apps — OAuth 2.1, OIDC, DPoP, JWT rotation, cookie security, RBAC vs ABAC vs ReBAC rubric.
hatch3r-dotnet-patterns
.NET 10 + C# 14 conventions covering minimal APIs, nullable reference types, async/await, Entity Framework Core, dependency injection, structured logging, and xUnit testing.
hatch3r-enhancability
CQ9 Enhancability Quality measurement rule — feature-flag adoption on user-visible behavior, config externalization, API versioning + deprecation policy, forward-compat patterns, extension-point definition.