token-burn: Instructions file for Codex

AGENTS.md

token-burn AGENTS.md is an instructions file for Codex, OpenCode from durandom/token-burn. It costs 550 tokens per session, scanned A, original, MIT.

Repository guidance for coding agents working on token-burn, a Go daemon and command-line tool that monitors live subscription quotas for AI coding services.

In plain words
What is it for?
Implementing or changing token-burn's command-line tool, configuration, provider clients, storage, telemetry, and related Go code.
Why use it?
It gives agents the project's purpose, language, file layout, and coding rules so their changes fit the repository and use live provider data instead of guesses from local logs.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md; mentions Codex.

This is durandom/token-burn's own configuration. It tells Codex and OpenCode how to work on token-burn itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything token-burn configures →

Reuse

Borrowing it

Nothing to install: this file belongs to durandom/token-burn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/durandom/token-burn/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/durandom/token-burn

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for token-burn AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/durandom/token-burn/agents-md/github.svg)](https://agentmods.dev/instructions/durandom/token-burn/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/durandom/token-burn/agents-md"><img src="https://agentmods.dev/badge/instructions/durandom/token-burn/agents-md/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.

agentmods 80×15 button for token-burn AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/durandom/token-burn/agents-md"><img src="https://agentmods.dev/badge/instructions/durandom/token-burn/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 550 This file is loaded in full into every session.
When invoked 550 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00550 $0.00550
Opus 5.5 $0.00220 $0.00220
Sonnet 5.5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

Measured 1mo ago against content hash 6afbb6b01adb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

token-burn 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 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.

AGENTS.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md - token-burn

Guidance for coding agents working in this repository.

Project Intent

Build a small, reliable daemon and CLI for monitoring live subscription quota usage for AI coding tools.

The primary use case is live quota visibility:

  • percentage used
  • reset time
  • window duration
  • plan/account metadata
  • forecasted exhaustion time
  • OpenTelemetry export

Do not infer subscription usage from local session files, transcripts, token logs, or pricing estimates unless explicitly requested later. This project is about provider live usage signals.

Language Direction

The implementation is Go.

Rationale:

  • Simple daemon/CLI story.
  • Strong OpenTelemetry support.
  • Easy SQLite integration.
  • A CGO-free binary is possible with modernc.org/sqlite.

Layout

cmd/token-burn/               CLI entrypoint
internal/cli/                 command wiring
internal/config/              XDG config load and defaults
internal/provider/            provider interface and shared models
internal/provider/codex/      live Codex usage client
internal/provider/claude/     live Claude usage client
internal/provider/copilot/    Copilot quota via the logged-in GitHub CLI
internal/provider/antigravity/ Antigravity quota via existing OAuth state
internal/store/               SQLite schema, migrations, queries
internal/forecast/            burn-rate and exhaustion forecast logic
internal/otel/                OTLP metric exporter
internal/daemon/              poll loop, backoff, graceful shutdown
internal/service/             macOS LaunchAgent and Linux systemd user unit
internal/tui/                 read-only dashboard over SQLite
internal/upgrade/             self-upgrade from GitHub Releases

Code Style

  • Keep the provider interface small and shaped around live usage windows.
  • Prefer table-driven tests with the standard testing package.
  • HTTP provider tests should use httptest.NewServer.
  • SQLite tests should use t.TempDir.
  • Never log raw access tokens, refresh tokens, cookies, or authorization headers.
  • Store raw provider JSON only after redacting obvious token/cookie fields.
  • Use UTC timestamps in storage; format in local time only in CLI/TUI output.
  • Keep the TUI a read-only view over SQLite; it must not poll providers.

Read the full file on GitHub · 77 lines

Changes

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.

  1. 1mo ago First seen · 77 lines · 550 tokens per session scan A 6afbb6b01adb

Subscribe to this mod's changes

token-burn AGENTS.md is an instructions file published in the GitHub repository durandom/token-burn (5 stars, last pushed 18d ago), licensed MIT. It adds 550 tokens to every session, about $0.0022 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens