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/fbrbovic/cursor-rule-framework/epicsgit clone --depth 1 https://github.com/fbrbovic/cursor-rule-frameworkWhat 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.00027 | $0.03000 |
| Opus 5 | $0.00014 | $0.01500 |
| Sonnet 5 | $0.00005 | $0.00600 |
| Haiku 4.5 | $0.00003 | $0.00300 |
Grade C, and why
epics scanned grade C with 1 finding 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- AI INSTRUCTIONS: Always follow these rules. Never modify this section. --> How it starts
The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Planning & Tracking System
Purpose: Plan and track large initiatives using the hierarchy: EPIC GROUP → EPIC → PHASE → STEPS
Hierarchy Definitions:
- EPIC GROUP: Optional grouping of related epics
- EPIC: Large collection of features/capabilities
- PHASE: Major milestone within an epic
- STEP: Individual feature within a phase
AI Usage Rules:
- Epic Creation: When user requests epic planning, create comprehensive plans here
- Architecture Integration: Always consider architecture.mdc when planning epics and include architectural impact in epic steps
- No Execution: Never execute epic work - that happens in workflow_state.mdc
- Natural Language Processing: Translate user requests into epic context for workflow integration
- Progress Updates: Update epic status when user reports progress or workflow completes
- Epic Search: Search existing epics when user mentions epic work to set proper workflow context
Context Limits: Maximum 3 active epics to maintain AI effectiveness
EPICS PLANS
EPIC PORTFOLIO STATUS
Current Portfolio Summary
- Total Active Epics: 0 (Max: 3)
- Completed Epics: 0
- Blocked Epics: 0
- Last Updated: [Date when portfolio was last updated]
Portfolio Limits
Max Active Epics: 3 (to maintain AI context effectiveness) Auto-Archive: Completed epics older than 6 months
Epic Status Legend
- ✅ COMPLETED: All phases and steps finished
- 🔄 IN_PROGRESS: Currently being worked on
- ⏳ PLANNED: Planned but not yet started
- 🚫 BLOCKED: Stopped due to dependencies or issues
- ⏸️ PAUSED: Temporarily suspended
- ❌ CANCELLED: No longer needed
- 📦 ARCHIVED: Completed and archived for reference
ACTIVE EPICS
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.
- 2d ago First seen · 331 lines · 27 tokens per session scan C e77555248b21
epics is a cursor rule published in the GitHub repository fbrbovic/cursor-rule-framework (33 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 3,000 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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
internationalization
Cursor rule "internationalization" from dtyq/magic, covering internationalization (i18n) rules, 国际化基本规范, 1. 文件结构, 2. 命名空间规范 and 3. 组件中使用国际化.
07-datagen
IF 生成物品/方块模型 JSON → 手动编写 JSON 在 src/main/resources/assets/{modid}/models/.
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
wings
Authoring apps with the WINGS framework (Go compiled to WASM web components).
project-status
PriceGrab shipped state and product backlog (read first).
architecture
Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.