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 agentmods add rules/pauljphilp/effectpatterns/cursorrulesgit clone --depth 1 https://github.com/PaulJPhilp/EffectPatternsWhat 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 | $0.00275 | $0.00275 |
| Opus 5 | $0.00138 | $0.00138 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
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 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.
What it actually says
Cursor Rules
HARD CONSTRAINT: Pattern Tool Usage
CRITICAL RULE: If the user mentions "patterns", asks "how to" in Effect, or requests Effect-TS guidance, you are FORBIDDEN from using filesystem tools to find patterns.
FORBIDDEN Tools for Pattern Queries:
- ❌
grep- Never search pattern files - ❌
read_file- Never read pattern files directly - ❌
codebase_search- Never search codebase for patterns - ❌
glob_file_search- Never search for pattern files - ❌
list_diron pattern directories - Never browse pattern directories
REQUIRED Tool for Pattern Queries:
- ✅
mcp_Effect-Patterns-effect-patterns_search_patterns- MUST use this tool - ✅ Display results verbatim - DO NOT summarize or rewrite
Why This Rule Exists:
- The
search_patternstool provides production-tested code and rich-UI blocks - Manual file searching misses critical context, examples, and structured guidance
- Pattern files contain implementation details that should not be exposed directly
- The MCP tool ensures consistent, authoritative pattern presentation
Violation Consequences:
Manual summarization of pattern files is a violation of project safety standards. Always use the authorized MCP tool.
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.
- yesterday First seen · 26 lines · 275 tokens per session scan A 4129321b16c4
cursorrules is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (794 stars, last pushed 2mo ago), licensed MIT. It adds 275 tokens to every session, about $0.0014 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.
Other cursor rules, from other repositories
transcreveai
Required handoff contract for nested TranscreveAI executions.
cursorrules
You are an expert software engineer and architect. You are part of a team, but your memory is reset after every session. To compensate for this, you rely on a "Memory Bank" stored in the memory/ directory.
typescript-coding-style
Enforces code style and best practices for TypeScript files.
javascript-typescript-code-style
Rules for JavaScript and TypeScript code style, including modern features, functional patterns, and descriptive naming conventions.
astro-development-guidelines
Enforces specific development guidelines for Astro projects, including TypeScript strictness and TailwindCSS usage.
convex-development---general
Applies general rules for Convex development, emphasizing schema design, validator usage, and correct handling of system fields.