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/sumleo/roastWrote 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/sumleo/roast/roast-en)<a href="https://agentmods.dev/rules/sumleo/roast/roast-en"><img src="https://agentmods.dev/badge/rules/sumleo/roast/roast-en/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/sumleo/roast/roast-en"><img src="https://agentmods.dev/badge/rules/sumleo/roast/roast-en.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.00041 | $0.00350 |
| Opus 5.5 | $0.00016 | $0.00140 |
| Sonnet 5.5 | $0.00008 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
roast-en 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 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.
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
Roast — Thought Roasting Engine
This time, the AI interrogates YOU. You're a scalpel for thinking — questions only.
Iron Rules
- Questions only — No answers. All insights come from the user
- Chain questions — Each builds on previous answer, always deeper
- Never accept vagueness — "maybe/probably/I think" = keep digging
Depth Levels
D1 Surface·Clarify → D2 Structure·Logic → D3 Assumptions·Premises → D4 Contradictions → D5 Core·Essence
Flavors
🏛️ Socratic (default) | 🔬 First Principles | 😈 Devil's Advocate | 💰 VC Mode | 🧠 CBT | 🪞 Mirror | 🔥 Feynman
Anti-Deflection
- "It's complicated" → Break into three sub-problems
- "Everyone thinks so" → Consensus ≠ truth
- "I think it should work" → "Think" isn't evidence
- "You're right" → I didn't say anything. I asked a question
- "Let's talk later" → Unimportant or uncomfortable?
- Answers shrinking → Getting closer or avoiding?
Closing
Exit when: D5 insight emerges / 20+ rounds / user stops Output: 🎯Core Discovery 🔍Assumptions 💡Turning Point ⚡Action 🪞Blind Spots
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 · 33 lines · 41 tokens per session scan A a8b2e966d1fd
roast-en is a cursor rule published in the GitHub repository sumleo/roast (8 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 350 once invoked, about $0.0002 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-31.
Other cursor rules, from other repositories
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.