AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 5, 2026, 10:00 JST

Claude Code's 25.5k token fixed cost — kou trims Memory to 4.2k

Claude Code's 25.5k token fixed cost — kou trims Memory to 4.2k

3 Key Points

  1. What happened

    Gakken LEAP engineer kou ran /context in a new Claude Code session and found 25.5k tokens already loaded before asking anything, including System prompt 5.7k, System tools 6.4k, Skills 6.0k and Memory 7.3k. After dropping 14 memory entries, Memory fell to 4.2k.

  2. Why it matters

    That fixed cost is charged per session, so it is the first place to look when a coding agent feels expensive — and trimming stale memory is the concrete, measurable win kou found.

  3. What to watch

    The savings hinge on whether stale memory is what is inflating the load, since old entries can make the agent act as if it already knows the answer. kou's rule: before writing to memory, decide where it belongs.

WHO IT HITSDevelopers and engineering teams running coding agents like Claude Code on fixed subscriptions are the people who feel this directly, since every session pays the fixed context load before any work begins.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The article is a first-person measurement exercise, not a vendor announcement. kou starts from a familiar frustration — a 200k-token conversation window filling in a few turns and a weekly quota nearly exhausted by midweek — and decides to map where tokens actually go before paying for a higher plan.

The sequence matters. The first stop is the cost that exists before any conversation: running /context in a fresh Claude Code session reveals System prompt, System tools, Skills, Memory and Custom agents already loaded. Only then does the piece move to caches, long conversations, reasoning levels and code-search tools, and each later finding is framed as a layer on top of that fixed base. Memory is where kou found the clearest gain, cutting 7.3k to 4.2k tokens by deleting expired, duplicated and unused entries, and adding a roughly 60-token, two-line rule to CLAUDE.md to keep it from creeping back.

The stakes here are modest but concrete: whether the reader can keep working on a $20 monthly subscription rather than upgrading. That hinges on whether the same pattern — a large fixed load, stale memory, repeated prefixes — holds in their own repository, since the boundaries kou reports, such as the felt change around 350k tokens, are described as personal impressions that vary by task.

FAQ
How much of a Claude Code session is already used before I type anything?
kou measured 25.5k tokens, made up of System prompt 5.7k, System tools 6.4k, Skills 6.0k, Memory 7.3k and Custom agents 80 tokens.
How did kou reduce the Memory cost?
By removing 14 entries in one cleanup: five expired, six rules duplicated in skills, and three that were never used. Memory dropped from 7.3k to 4.2k tokens.
What is the risk of keeping old memory entries?
kou says old memory is worse than none: with no record the agent goes and checks, but with an old record it assumes it already knows and gets things wrong.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAkamai lands $11.6 billion Anthropic AI infrastructure deal