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/labsai/EDDIWrote 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/labsai/eddi/project-context)<a href="https://agentmods.dev/rules/labsai/eddi/project-context"><img src="https://agentmods.dev/badge/rules/labsai/eddi/project-context/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/labsai/eddi/project-context"><img src="https://agentmods.dev/badge/rules/labsai/eddi/project-context.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.00090 | $0.00090 |
| Opus 5.5 | $0.00036 | $0.00036 |
| Sonnet 5.5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
project-context 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 16d 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
Read and follow all instructions in the repository root file AGENTS.md.
When working under ui/manager/ also follow ui/manager/AGENTS.md and ui/manager/CLAUDE.md; under ui/chat/, ui/chat/AGENTS.md.
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.
- 16d ago Changed · +2 lines · +45 tokens per session 3bb64b63c877
- 1mo ago First seen · 8 lines · 45 tokens per session scan A 7a684a9a306a
project-context is a cursor rule published in the GitHub repository labsai/EDDI (384 stars, last pushed today), licensed Apache-2.0. It adds 90 tokens to every session, about $0.0004 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 cursor rules, from other repositories
issues-java
Java endpoint, repository, and entity conventions.
scopes
Java SDK Hubs and Scopes.
springboot-jpa-best-practices
A set of Chinese-language rules for structuring Java Spring Boot applications that use JPA, a library for database access.
graftcode-java
Mandatory Graftcode architecture rules for building Java backend services (plain Maven/Gradle modules exposed via Graftcode Gateway, not REST).
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
issues-format-imports
Java import order and formatter alignment.