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/durandom/token-burnWrote 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/durandom/token-burn/beads)<a href="https://agentmods.dev/rules/durandom/token-burn/beads"><img src="https://agentmods.dev/badge/rules/durandom/token-burn/beads/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/durandom/token-burn/beads"><img src="https://agentmods.dev/badge/rules/durandom/token-burn/beads.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.00596 | $0.00596 |
| Opus 5.5 | $0.00238 | $0.00238 |
| Sonnet 5.5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
beads 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 2d 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.
This is a copy
100% identical to beads — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Issue Tracking
This project uses Beads (bd) for issue tracking.
Core Rules
- Track ALL work in bd (never use markdown TODOs or comment-based task lists)
- Use
bd readyto find available work - Use
bd createto track new issues/tasks/bugs - Treat commit, push, and Dolt remote sync as policy-controlled handoff actions
- Run
bd primefor complete workflow context (SSOT for operational commands) - Default to conservative git authority: report status and proposed commands unless the user, orchestrator, or repository profile explicitly authorizes commit/sync/push
Quick Reference
bd prime # Load complete workflow context (SSOT)
bd ready # Show issues ready to work (no blockers)
bd list --status=open # List all open issues
bd create "title" -t task -p 2 # Create new issue
bd update <id> --claim # Claim work atomically
bd unclaim <id> # Release stuck issue (agent crashed)
bd close <id> # Mark complete
bd dep add <issue> <depends-on> # Add dependency
bd dolt push # Sync with remote when authorized
Workflow
- Check for ready work:
bd ready - Claim an issue atomically:
bd update <id> --claim - Do the work
- Mark complete:
bd close <id> - Handoff: report changed files, validation, issue status, and any proposed commit/sync/push commands
Issue Types
bug- Something brokenfeature- New functionalitytask- Work item (tests, docs, refactoring)epic- Large feature with subtaskschore- Maintenance (dependencies, tooling)
Priorities
0- Critical (security, data loss, broken builds)1- High (major features, important bugs)2- Medium (default, nice-to-have)3- Low (polish, optimization)4- Backlog (future ideas)
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.
- 2d ago First seen · 68 lines · 596 tokens per session scan A 6b6ad52e515d
beads is a cursor rule published in the GitHub repository durandom/token-burn (6 stars, last pushed 3d ago), licensed MIT. It adds 596 tokens to every session, about $0.0024 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to beads, differing in 0 lines, and is treated as a copy.
beads compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| beadsdurandom/token-burn | Cursor rule | 6 | 3d ago | MIT | A | 596 | Cursor |
| ponytailDietrichGebert/ponytail | Cursor rule | 190k | 15d ago | MIT | A | 604 | Cursor |
| angular-20angular/angular | Cursor rule | 101k | today | MIT | A | 0 | Cursor |
| dev-standardapache/superset | Cursor rule | 76k | today | Apache-2.0 | A | 1,147 | Cursor |
| prefer-direct-imports-over-module-mocksprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 0 | Cursor |
| config-validation-and-normalizationprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 0 | Cursor |
| control-plane-descriptorsprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 0 | Cursor |