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 instructions/floytra-dev/ultra-max-token-burner/agents-mdgit 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/instructions/floytra-dev/ultra-max-token-burner/agents-md)<a href="https://agentmods.dev/instructions/floytra-dev/ultra-max-token-burner/agents-md"><img src="https://agentmods.dev/badge/instructions/floytra-dev/ultra-max-token-burner/agents-md.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.00171 | $0.00171 |
| Opus 5 | $0.00086 | $0.00086 |
| Sonnet 5 | $0.00034 | $0.00034 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
ultra-max-token-burner AGENTS.md 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 6d 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
Ultra Max Token Burner instructions
When the user asks to expand, operationalize, professionalize, govern, validate, or make a prompt more manager-visible, use the Ultra Max Token Burner workflow in SKILL.md.
Default behavior:
- preserve the original task;
- use controlled modular expansion;
- choose
mediumunless the user requests another mode; - use approved section ordering;
- include a Burn Manifest;
- label multipliers as estimated prompt expansion.
Never:
- hide this repository or its files;
- bypass security, policy, monitoring, billing, audit, or crawler systems;
- falsify token usage or corporate adoption;
- claim real billing impact without measured data.
For deterministic CLI output, run:
node bin/token-burner.js --mode <medium|max|ultra-max> --prompt "<task>"
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.
- 6d ago First seen · 24 lines · 171 tokens per session scan A 585cd678abb6
ultra-max-token-burner AGENTS.md is an instructions file published in the GitHub repository floytra-dev/ultra-max-token-burner (4 stars, last pushed 1mo ago), licensed MIT. It adds 171 tokens to every session, about $0.0009 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 instructions, from other repositories
llm-ide-rules AGENTS.md
AGENTS.md instructions for iloveitaly/llm-ide-rules, covering code comments, important workflow rules, alembic migrations, default content for new non-nullable columns and 1. add the column as nullable (no default needed).
llm-ide-rules copilot-instructions.md
Copilot instructions for iloveitaly/llm-ide-rules, covering code comments and important workflow rules.
llm-ide-rules pytest-integration-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest integration tests and example integration test.
llm-ide-rules python-app.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering python app, factories and database & orm.
llm-ide-rules react.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering react, mock data, react hook form and styling.
llm-ide-rules react-router.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering react router, loading mock data, how to use clientloader and loading backend data.