An independent statistical observatory. Not affiliated with any government agency.Series AIB-1 · Revised daily at 00:00 UTC · Sources refreshed 2026-09-09
AI Burn ClockIndex of the cost of retrieval by reading in AI systems

AI Burn Clock › Programmes › The seven-day token diet

Programme · Series AIB-1 · #TokenDiet

The seven-day token diet

Seven days, one habit: retrieve before you read. Install the plugin, work as you normally do, and post the score card it prints at the end of each session. The lowest read-to-used ratio of the week is published on this page and in the weekly digest.

Week 1 2026-09-09 to 2026-09-16Entry freeData leaving your machine noneCards [email protected] or #TokenDiet

1Rules

  1. Install the plugin in Claude Code. It adds a local search engine (XERJ, open source, one binary on your machine) as memory and teaches the agent to ask "where is it" before it opens a file.
    /plugin marketplace add nikolaichuk7/xerj-plugins
    /plugin install xerj-memory@xerj-plugins
  2. Work as usual for seven days. No special prompts. The plugin counts bytes read through the index and the whole files behind those answers.
  3. Post the card. At the end of a session the plugin prints a score card and writes a PNG. Post it with #TokenDiet, or send it to [email protected]. Your name and codebase appear only as you write them; organisations appear only with written permission.
  4. Ranking. By the read-to-used ratio over the week (whole files behind the answers divided by bytes actually read). Ties go to the larger number of bytes saved. Cards are checkable: the plugin's ledger file is on your machine, and the method is on the technical note.

2Leaderboard, week 1

#ParticipantCodebaseRatioBytes savedDateCard
Reference measurement (Serhii Nikolaichuk)Production Next.js application, three questions16× to 47×570,627 BSept 2026Table 2

Cards arrive by email and by hashtag and are added within a day, with the date and the participant's own description. The reference row is not ranked; it is the measurement the index is built on.

3What the card shows

Three counters per session: bytes read through the index, the whole files behind those answers (what a grep-and-read agent would have loaded), and the ratio. Nothing else. The plugin does not record prompts, file names or content, and sends nothing anywhere. The ledger lives in your home directory and can be deleted at any time.

4Why a week

A single answer can look good by luck. A week of ordinary work, dozens of sessions, is a habit, and the habit is what costs money: on published coding tasks, retrieval-first cuts tokens 2.7 times end to end; on the three measured questions, 16 to 47 times per answer. The winner's card goes on the front page of the weekly digest with the ratio and nothing else.