Skip to content

Topic

LLM token costs

The metered per-token cost of running large language models, and the budgeting and measurement practices teams use to keep it predictable.

Current stories

buildOne report1 publisher

Short action lists in place of full UI-tree reads cut a macOS agent's task cost by 85%

beans-picker cut a median macOS agent task from $0.388 to $0.060 in its author's benchmark by replacing full UI-tree reads with short candidate lists. Whether that carries over depends on how much of your own agent's bill goes to reading the window.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap+20
Incentives60
Confidence40
buildOne report1 publisher

Dev's math suggests the supervisor LLM drove most of a reported 70% token cut, if handoff truly costs zero tokens

An engineer writing on dev.to swapped the coordinating LLM in a multi-agent system for an XState machine and typed receipts, reporting a 70% token cut. Whether that transfers depends on what your coordinator cost.

Publishers:dev.to

Reality

Evidence30
Adoption15
Hype gap+40
Incentives45
Confidence35
buildOne report1 publisher

A rerun of the same SWE-bench task can consume 30 times the tokens

A study of eight frontier models on SWE-bench Verified puts agentic coding at roughly 1,000 times the token cost of code chat, dominated by input, with the models' own pre-run estimates correlating no better than 0.39.

Publishers:arxiv.org

Reality

Evidence60
Adoption
Not scored
Hype gap+15
Incentives30
Confidence55
buildOne report1 publisher

Every turn pays again for the same MCP tool definitions

A post arguing the Model Context Protocol was built for 2024-era models pushed a 165-point Hacker News thread into a fight about token cost. The post reports no benchmark, so the measurement is left to your own agent.

Publishers:dev.to

Reality

Evidence28
Adoption
Not scored
Hype gap+30
Incentives40
Confidence46
buildOne report1 publisher

Alibaba's Open Code Review hands file picking and line positioning back to deterministic code

Alibaba ran the reviewer internally for two years across tens of thousands of developers before releasing it. The write-up is specific about how files get selected and comments get positioned, and it stops short of publishing the benchmark scores.

Publishers:dev.to

Reality

Evidence32
Adoption30
Hype gap+55
Incentives68
Confidence38
buildOne report1 publisher

Markup filled 263,968 of a scraped product page's 267,361 tokens

Decodo's own runs on ten pages put raw HTML at 3 to 24 times the token count of the same pages as Markdown, with every model still answering correctly and the JSON-LD fields lost in the conversion.

Publishers:dev.to

Reality

Evidence52
Adoption
Not scored
Hype gap+12
Incentives88
Confidence44
buildOne report1 publisher

A compiler gate in a shadow worktree decides which LLM patch reaches the repo

Sergi Corruchaga reports his D-Engine harness produced the same diff as DeepSeek's official agent on 42 times fewer tokens, by letting the model propose SEARCH/REPLACE blocks and a local runtime apply them.

Publishers:dev.to

Reality

Evidence32
Adoption8
Hype gap+30
Incentives82
Confidence45
leadershipOne report1 publisher

McKinsey meters its consultants' AI tokens like mobile data on a work phone

Consumption pricing made model access a variable cost, and McKinsey now watches it user by user, emailing the heavy spenders rather than cutting them off. EY reports a larger saving from a quieter method.

Reality

Evidence46
Adoption61
Hype gap+14
Incentives74
Confidence54
buildOne report1 publisher

Spotify's shunt hook blocks non-targeted Claude Code file reads past a configurable line threshold

The 90 percent token saving is one engineer's own usage on his own repos, but the enforcement mechanism underneath it copies cleanly: a line-count threshold that returns a block, with a pipe-shaped hole in it.

Publishers:engineering.atspotify.com

Reality

Evidence44
Adoption18
Hype gap+30
Incentives72
Confidence52