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/imMamdouhaboammar/get-fableWrote 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/immamdouhaboammar/get-fable/cursor-fable-rules)<a href="https://agentmods.dev/rules/immamdouhaboammar/get-fable/cursor-fable-rules"><img src="https://agentmods.dev/badge/rules/immamdouhaboammar/get-fable/cursor-fable-rules.svg" alt="Measured on agentmods" 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.00197 | $0.00197 |
| Opus 5 | $0.00098 | $0.00098 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
cursor-fable-rules 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 3d 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.
What it actually says
Cursor Fable Lifecycle Rules
Follow the get-fable coding lifecycle for all engineering tasks in this project.
Core Rules
- Route Before Coding: Run
get-fable route "<task>" --applywhen selecting a lifecycle phase. - Durable Cards: Work on one bounded card in
.fable/LEDGER.md(get-fable card "<card>"). - Mutation Tracking: Every file edit invalidates previous test verification.
- Evidence Verification: Record typed evidence (
get-fable evidence pass test "<tool>" "<detail>"). - Failure Recovery: On repeated test or command failures, enter
fable-recoverand diagnose root cause before attempting fixes. - Situational Prediction: Query
get-fable sparkfor the single atomic next move.
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.
- 3d ago First seen · 19 lines · 197 tokens per session scan A 20bae8f3857c
cursor-fable-rules is a cursor rule published in the GitHub repository imMamdouhaboammar/get-fable (3 stars, last pushed 3d ago), licensed MIT. It adds 197 tokens to every session, about $0.0010 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-09-05.
Other cursor rules, from other repositories
loop
Schedule a recurring instruction or command with an interval; use for /loop, loop status, or loop stop, with native scheduling or an external macOS/Linux/WSL/Windows driver.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.