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/fbrbovic/cursor-rule-frameworkWrote 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/fbrbovic/cursor-rule-framework/epics)<a href="https://agentmods.dev/rules/fbrbovic/cursor-rule-framework/epics"><img src="https://agentmods.dev/badge/rules/fbrbovic/cursor-rule-framework/epics/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/fbrbovic/cursor-rule-framework/epics"><img src="https://agentmods.dev/badge/rules/fbrbovic/cursor-rule-framework/epics.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.00027 | $0.03000 |
| Opus 5.5 | $0.00011 | $0.01200 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (36 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 3,000 once invoked, about $0.0001 per session on Opus 5.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
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.