Source: raw/Paste_This_Into_Claude_Code_Never_Run_Out_Of_Tokens_Again.md and raw/Paste_This_Into_GPT-6_Astra_Never_Run_Out_Of_Tokens_Again.md (auto-caption transcripts)
Creator: Sharbel (YouTube @sharbelxyz) · URLs: https://www.youtube.com/watch?v=kHtOSJRUkLs (Claude Code, 19:48, uploaded 2026-08-19) and https://www.youtube.com/watch?v=XgMhU4CE-lQ (GPT-6 Astra and Codex, 11:59, uploaded 2026-09-19) · No sponsors. Both offer a free audit prompt in the description (“you don’t have to give me your email”).
Two companion videos with one argument: almost none of your usage is what you type. Sharbel measured his own Claude Code logs at 0.01% typed text and 96% rereading history, then lists the fixes in order of what they save. The Claude Code video leans on Anthropic’s docs; the Codex video on OpenAI’s guidance and Artificial Analysis numbers. Both quote first-party figures that were not rechecked here.
Key Takeaways
- Every turn resends the whole conversation. “A 3,000 token file your agent reads at turn four of a 40-turn session … costs you 3,000 tokens 37 more times.”
/clearbetween jobs is the biggest free saving, because it resets the base every other cost is a fraction of. Run/renamefirst so/resumecan bring the session back.- Switching model mid-session is the most expensive move. Cache reads cost about a tenth of normal input, and the model is part of the cache key. His Opus 5 example: at 200,000 tokens of context a 10-cent turn becomes a 1-dollar turn.
- Also breaks the cache, per his reading of Anthropic’s docs: changing effort, fast mode, connecting or disconnecting an MCP server when tools load up front, enabling a plugin that ships an MCP server, compacting, and resuming a long session after upgrading Claude Code (“the most expensive request you will send”).
- Safe: editing repo files or the memory file, output style, permission mode, invoking skills and commands, recaps, rewinds, spawning a subagent.
- Filter command output. An install can dump 800 lines into the conversation. Ask the agent to write a small filter between itself and noisy commands; he says Anthropic ships a working example that cuts tens of thousands of tokens to hundreds.
- Tool manuals. GitHub’s MCP costs about 26,000 tokens and Slack’s about 21,000, he says. Claude Code now defers tool instructions (loads a contents page and opens a section when needed), which he puts at an 85% cut; check that
/contextshows the tools line as deferred. Turn off connectors unused for a month. With deferral on, toggling tools mid-session only appends and does not rebuild the cache. - Subagents move tokens, they do not save them. His reading of Anthropic’s example: a subagent reads about 6,000 tokens and returns a 420-token summary, but loads its own system prompt, memory file and tools, burning about 9,800 tokens to save 5,700. Worth it only when the output is large, you will not need the detail again, and the session will run many more turns. Set subagents to Haiku. He also quotes Anthropic’s multi-agent research post: agents use about 4x the tokens of chat, multi-agent systems about 15x.
- Scheduled tasks are the hidden doubler. Each fire sends the full attached context. The subscription cache lasts an hour, so a task that runs less often than hourly misses the cache every time and pays full price; running every 45 minutes can be cheaper than every 2 hours. He cites Anthropic’s figure for an idle background session at under 4 cents.
- Myths he rejects:
- Shorter prompts: a rounding error. Vague prompts cost through rework, not length.
- Compacting to save money: it resends the whole conversation to summarise it, then wipes the cache. “Compaction buys you continuity, not savings.” Use
/rewindto undo a few turns instead. - Screenshots of text: about 2,700 tokens per screenshot on Opus 5, nearly 5,000 at 4K. Paste the text.
- PDFs: 1,500-3,000 tokens per page for the text plus an image of the page. Convert to plain text first, for about a quarter of the cost.
- Meters.
/context(what is in the window),/usage(what burned your plan, by skill, tool and agent),/cost(this session, history versus new work), and the burn-rate meter. Session logs on disk record the cost of every reply; ask a subagent to compute your own typed-text percentage.
Codex and GPT-6 Astra specifics
- Effort is the biggest lever. Levels: light, medium, high (default), extra high, ultra. His Artificial Analysis figures: about 3.26 at max, and about $7 a task at max on its coding benchmark. OpenAI’s guidance, as he quotes it: lower effort does not mean lower capability. Start at medium and step up.
- Fast mode doubles the rate. Turn it off unless you need the speed.
- Make Astra the boss, not the worker. Cheapest model (he names GPT-5.5) for scoping and cleanup, a mid-tier model (GPT-5.6 Sol or Luna) for planning and checklists, Astra on medium for the final judgment call. Set this up once as Codex subagents, either in a
.tomlfile in the project or with three prompts he provides. His claim: one video’s cost fell from 1. - Long-context price step. Above about 272,000 input tokens, the whole request is repriced: 2x for input and 1.5x for output. Keep working context well under that;
/statusshows it. - Plugins. Settings, Plugins: turn off anything unused for a month. He reports others going from a 55,000-token load to 3,000.
- Output filters. RTK (free) returns stripped-down command output; on Codex you must tell it to use RTK. His test: a large file listing went from 7 million characters to about 1,000. Headroom does the same across Claude Code and Codex; its maker claims about half the cost.
Topic: whether
/compactsaves tokensExisting claim: (from Claude Code Token Optimization, hacks 12 and 13) — compact manually at about 60% context, and “Run
/compactor/clearbefore walking away” to avoid a cache-miss spike. New source says: (fromraw/Paste_This_Into_Claude_Code_Never_Run_Out_Of_Tokens_Again.md) — compacting “is the single most expensive message of the session” because it resends the full conversation, then “wipes your cache on purpose”. “Clearing is free. Compaction buys you continuity, not savings.” Status: unresolved. The two may fit together: compacting early can protect answer quality, and a compact while the cache is warm costs less than one after it goes cold (see the r/ClaudeAI caching signal in that article). Neither source measures it. Treat/clearas the saving and/compactas a quality tool.
Try It
- Paste his audit prompt (in the video description) or ask: “Read my context breakdown, check whether tool deferral is on, measure my memory files, look at my cache hit ratio and list scheduled tasks.” Fix the biggest item first.
- Make it a rule to pick model and effort before the first message.
- Run
/context, confirm the tools line says deferred, and switch off connectors unused in the past month. - Open your scheduled tasks and check how often each fires against the one-hour cache window.
- In Codex, start on medium effort and turn off fast mode.
Open Questions
- The 85% deferral cut, the 26,000 and 21,000 token MCP sizes and the 9,800-versus-5,700 subagent example are his readings of Anthropic material; the pages were not read here.
- The 272,000-token repricing threshold for Astra should be checked against OpenAI’s pricing page and GPT-6 Astra, Sol and Luna.
- RTK’s 7-million-character result conflicts with independent tests in this wiki that found RTK saved little (see the contradiction in Token Optimization). His test was one large file listing, the case RTK suits best
Related
- Claude Code Token Optimization — the older 18-hack list and the RTK tests
- Claude 5.5 Mistakes and Fixes — the one-hour cache and usage habits
- Model vs. Effort — first-party explanation of the two settings
- Subagents — the delegation trade-off
- Headroom — the compression layer he mentions
- Image-as-Context Token Arbitrage — a source that argues images can be cheaper, the opposite of his screenshot advice in some cases
- Token Economics Primer
- Claude Code in 30 Minutes (Sharbel)