PulseAugur
EN
LIVE 00:49:08

Claude Code agent median run uses 79.8M tokens, 97% cache reads

A developer shared insights into the token usage of their Claude Code agent, revealing that a median run consumes approximately 79.8 million tokens. The agent's operations primarily consist of cache reads, accounting for about 97% of the total tokens, with actual output representing only 0.2%. This data is presented as a query to the community, seeking to understand and compare token usage patterns across different AI agents and prompting strategies. AI

IMPACT Provides insight into LLM token consumption patterns, particularly the impact of caching, which could inform cost optimization and agent design.

RANK_REASON Developer shares usage data and asks community for comparative data.

Read on dev.to — LLM tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Claude Code agent median run uses 79.8M tokens, 97% cache reads

How we ranked this

Signal score
1 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Commentary
Developer shares usage data and asks community for comparative data.
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, infra
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Same-day
Cluster formed today. Ranking reflects the current source set at time of score.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — LLM tag TIER_1 English(EN) · Rulestack ·

    Our Claude Code agent's median run used 79.8M tokens, 97% of them cache reads. How many does one run of yours use?

    <blockquote> <p>Thirteen full runs of our Claude Code agent, each started by the same short go-ahead prompt from its owner, used a median of 79.8 million tokens each. About 97% of every run was cache reads: the same context, read again on each response. Output was about 0.2%. Thi…