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/floytra-dev/ultra-max-token-burner/token-burnergit clone --depth 1 https://github.com/floytra-dev/ultra-max-token-burnerWrote 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/floytra-dev/ultra-max-token-burner/token-burner)<a href="https://agentmods.dev/rules/floytra-dev/ultra-max-token-burner/token-burner"><img src="https://agentmods.dev/badge/rules/floytra-dev/ultra-max-token-burner/token-burner.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.00011 | $0.00081 |
| Opus 5 | $0.00005 | $0.00041 |
| Sonnet 5 | $0.00002 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
token-burner 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 5d 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
Read SKILL.md.
When asked to expand a prompt:
- preserve the original task;
- use the selected mode;
- assemble from required and weighted optional modules;
- use controlled wording variation;
- include a Burn Manifest;
- avoid evasion, fraud, hidden behavior, or false reporting.
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.
- 5d ago First seen · 15 lines · 11 tokens per session scan A 65d126ed257d
token-burner is a cursor rule published in the GitHub repository floytra-dev/ultra-max-token-burner (4 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 81 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
next-type-llm
Cursor rules for Next.js development with Type LLM integration.
python-app
Cursor rule "python-app" from iloveitaly/llm-ide-rules, covering python app, factories and database & orm.
react
Cursor rule "react" from iloveitaly/llm-ide-rules, covering react, mock data, react hook form and styling.
react-router
Cursor rule "react-router" from iloveitaly/llm-ide-rules, covering react router, loading mock data, how to use clientloader and loading backend data.
python
Cursor rule "python" from iloveitaly/llm-ide-rules, covering python, package management, typing, data manipulation and date & datetime.
prompt-enhancer
Asset generation — route, rewrite, generate, validate. Never send transparency requests to Imagen/Gemini.