project-context

A project-context rule telling coding agents to read the repository's root AGENTS.md file before working on the EDDI Backend.

In plain words
What is it for?
Use it at the start of EDDI Backend tasks to locate and follow the repository-specific instructions.
Why use it?
It directs agents to the project's full architecture and coding guidance before they make changes.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/labsai/eddi/project-context
Clone the repo
git clone --depth 1 https://github.com/labsai/EDDI

Made for: Cursor.

Per session 45 This file is loaded in full into every session.
When invoked 45 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.00045
Opus 5 $0.00023 $0.00023
Sonnet 5 $0.00009 $0.00009
Haiku 4.5 $0.00005 $0.00005

Measured yesterday against content hash 7a684a9a306a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.cursor/rules/project-context.mdc · 8 lines

What it actually says

Read and follow all instructions in the repository root file AGENTS.md.

Changes

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.

  1. yesterday First seen · 8 lines · 45 tokens per session scan A 7a684a9a306a

Subscribe to this mod's changes

project-context is a cursor rule published in the GitHub repository labsai/EDDI (372 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session, about $0.0002 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.