Borrowing it
Nothing to install: this file belongs to tbobm/dont-burn-it-all. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tbobm/dont-burn-it-all/main/.claude/skills/burn/SKILL.mdgit clone --depth 1 https://github.com/tbobm/dont-burn-it-allWrote 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/skills/tbobm/dont-burn-it-all/burn)<a href="https://agentmods.dev/skills/tbobm/dont-burn-it-all/burn"><img src="https://agentmods.dev/badge/skills/tbobm/dont-burn-it-all/burn/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/skills/tbobm/dont-burn-it-all/burn"><img src="https://agentmods.dev/badge/skills/tbobm/dont-burn-it-all/burn.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.00068 | $0.00896 |
| Opus 5 | $0.00034 | $0.00448 |
| Sonnet 5 | $0.00014 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
burn 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
burn is a CLI that spends your subscription 5-hour quota on real headless work and stops at a
threshold. Drive it in three steps; never re-implement its logic in the loop.
1. Ensure burn is installed, then configured
Locate the binary, preferring an installed one:
command -v burn || { test -x ./burn && echo "./burn"; } || echo "MISSING"
If it prints MISSING, ask the user how to install it (do not install silently) and offer:
- mise (prebuilt, no Go):
mise use -g "github:tbobm/dont-burn-it-all[exe=burn]@latest" - from source (in this repo):
go build -o ./burn .— then use./burn
Once you have a working burn command, verify config and relay the checklist:
burn setup
On any [FAIL] (no claude, no OAuth token, endpoint unreachable), report the remediation and
STOP — do not try to burn. [warn] lines are fine to proceed past.
2. Pick a mode
- Process a backlog (one session per Jira ticket, unattended): this is
burn process jiraand it has its own skill — useburn-jirainstead of this one. Anything about working labelled tickets, running while OOO/overnight/at the weekend, or reporting on such a run belongs there. - Launch (spend quota on a task): needs
--goal. Each launch runs--jobssessions to completion and stops — it does not loop. Start each launch deliberately.
Sessions prompt for permissions unless you passburn --goal "<real task>" --jobs 4 --target 80--dangerously-skip-permissions(opt-in; only with a throwaway--workdir). - Watch (governor only): polls usage every ~180s and notifies at the target, spawning nothing.
burn --watch --target 80
The first launch runs a ~3-minute preflight proving sessions bill to the subscription (not API).
This is intentional. If it hard-aborts, relay the fix (export CLAUDE_CODE_OAUTH_TOKEN=$(claude setup-token), unset ANTHROPIC_API_KEY) and stop.
3. Run it without blocking the loop (sub-agent + Monitor)
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 Changed · +10 lines 285eb3256ee3
- 12d ago First seen · 63 lines · 68 tokens per session scan A 9433bad8162d
burn is a skill published in the GitHub repository tbobm/dont-burn-it-all (9 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 896 once invoked, about $0.0003 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 skills, from other repositories
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press-score
Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side.
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…