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/Ethan-YS/project-brainWrote 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/ethan-ys/project-brain/cursorrules)<a href="https://agentmods.dev/rules/ethan-ys/project-brain/cursorrules"><img src="https://agentmods.dev/badge/rules/ethan-ys/project-brain/cursorrules/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/ethan-ys/project-brain/cursorrules"><img src="https://agentmods.dev/badge/rules/ethan-ys/project-brain/cursorrules.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.00827 | $0.00827 |
| Opus 5.5 | $0.00331 | $0.00331 |
| Sonnet 5.5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
cursorrules 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[Project Name] — Cursor Rules
This is the project-level instruction file for Cursor.
Layered above your global Cursor rules.
Write only what's specific to THIS project here.
First 30 seconds of a new session
Decide single- or multi-workstream (look at file naming under brain/):
- Only
STATUS.md/HANDOFF.md→ single-workstream branch - Multiple
STATUS_<workstream>.md→ multi-workstream branch (v2.1)
Single-workstream (default)
Must read (under brain/):
brain/MAP.md— project mapbrain/STATUS.md— current statebrain/HANDOFF.mdif it exists — previous session's still-warm thoughts
Then briefly report: project recognized + current progress + last blocker. Don't silently start working — confirm understanding first.
Multi-workstream (v2.1)
First read shared files: brain/MAP.md + brain/PROJECT.md.
Don't guess this window's workstream — use explicit signals only (the window is named for a workstream, e.g. web-6, or the user said so); otherwise ask:
"I see this is a multi-workstream project with [list workstreams]. Which one does this window work on?"
Then read brain/STATUS_<workstream>.md + brain/HANDOFF_<workstream>.md.
Concurrent windows (v2.8 — MAP §6 has a "Who's on it now" roster): also check other workstreams' STATUS for requests to yours still marked sent. Once the user confirms and work begins, write this window's name + date into your workstream's roster row (that cell only, committed alone) and say so.
If the user switches workstreams mid-session, re-read the new one's files and don't carry over memory.
Update responsibility
The AI never silently modifies a file in brain/ (tiered trust, METHODOLOGY §4.1): STATUS / HANDOFF / mechanical MAP registrations — write after the work lands, then announce what was written; DECISIONS / PROJECT / structural MAP changes — propose, then user approves.
Judgment division:
- The user decides "should we record now" (high-level pacing)
- The AI decides "specifically what to record / how to write each entry"
- The user has approval/rejection authority
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.
- 10d ago Changed · +3 lines · +221 tokens per session 2604a624e025
- 1mo ago First seen · 58 lines · 606 tokens per session scan A 68bc96891e40
cursorrules is a cursor rule published in the GitHub repository Ethan-YS/project-brain (173 stars, last pushed 11d ago), licensed MIT. It adds 827 tokens to every session, about $0.0033 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
cursorrules
You are an expert backend API developer. Follow these rules strictly for REST APIs, GraphQL servers, and microservices.
workflows
This rule applies universally to all AI-assisted code generation in this project.
review-checklist
This rule applies when AI needs detailed review guidance. It's fetched automatically when review-related tasks are detected.
guardrails
This rule applies universally to all AI-assisted code generation in this project.
core-principles
This rule applies universally to all AI-assisted code generation in this project.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.