GUIDES
4 Claude Token Hacks 📚
A lot of viral Claude cheat codes are useless. These are the 4 I actually use every day to get better answers while burning way fewer tokens, so you stop.
If you use Claude Code, "tokens" are basically your fuel. Every message, every file Claude reads, every tool it runs uses some up, and when you run low, things get slower and pricier. Most people have no idea where theirs are going, so they just burn through them and hope.
These four hacks are the ones I actually use, not the viral junk that doesn't move the needle. They get you better answers for less fuel, which is the whole game.
One Word First: Context
Your context window is Claude's short-term memory, everything it is currently holding in mind for your task. Tokens are how that memory gets measured. When people say a chat got "slow" or "dumb," it is usually because the context filled up with junk. Three of these four hacks are really about keeping that memory clean.
/context: See The Bloat
In Claude Code, type /context and hit enter. It pulls up a clear breakdown of exactly what is eating your context right now, split by category: system prompt, tools, skills, memory files, and your messages. Most people have never looked at this, so they have no idea their token usage is being eaten by, say, ten tools they never use or a giant file loaded at the start.
Once you can see it, you can fix it. Turn off connectors or tools you are not using in this project. Trim a bloated memory file. Notice that one huge document is hogging half your window. You cannot fix bloat you cannot see, and this is the one command that shows it to you.
/compact + /clear: Reset Smart
When your context is getting full, around the halfway point is a good habit, type /compact. It takes your whole conversation, summarizes it, and starts fresh with that summary loaded in, so you keep going without losing the important decisions. You shed the dead weight of every back-and-forth message but keep the conclusions.
The pro move most people miss: you can tell it what to protect. Type /compact keep the final database schema and the brand color codes exactly as written, and it will guard those details word for word while it trims the rest.
When you are done with one thing and moving to something totally unrelated, do not just keep typing in the same chat. Type /clear. It wipes the context back to empty so your new task starts clean, with none of the old baggage using up your window. Use /compact when you want to keep going on the same task, and /clear when you are starting something new.
Right Model For The Right Job
Not every task needs the most powerful model. Run a top model like Opus (or the brand-new Fable 5, released June 9, 2026) as your main agent for the work that actually needs brains: big decisions, planning the approach, reviewing code. That is where the smart model earns its keep.
Then have your subagents, the little helpers Claude sends off to do busywork like reading files, scraping pages, or searching, run on Haiku, the fast cheap model. The grunt work does not need genius, it needs speed. You set a subagent's model right in its definition file with a single line: model: haiku.
Redirect The Second It's Off
This is the most expensive mistake I see people make. Claude starts heading down the wrong path, and they just sit there and let it finish, watching it burn tokens building the wrong thing, so they can correct it after. That is double the cost: you pay for the wrong version, then pay again for the fix.
The second you see it going sideways, stop it (hit Esc in Claude Code) and redirect: "Stop, that is not what I meant. I want X, not Y." Catching it ten seconds in instead of two minutes in is one of the biggest token savers there is, and it is just a habit you build.
Make It Automatic
You can bake good token habits right into Claude so you do not have to remember them. Paste this into your CLAUDE.md file (your project's instruction file) and Claude will follow these rules every session.
Token-saving rules for your CLAUDE.md
What To Do With This
Open the CLAUDE.md file in your project (or create one in the main folder), and paste this in. New to .md files? They are just plain text notes Claude reads, see my crash course. You can also keep a personal copy and drop it into any project. Adjust any line to fit how you work, it is yours now.
The Real Win
Tokens stop being a mystery. You can see where they go, reset on purpose instead of by accident, put cheap work on the cheap model, and stop paying for wrong turns. Same quality answers, a fraction of the fuel, and you get way more done before you ever hit a limit.
The real unlock of AI agents is not full autonomy, but human-in-the-loop systems design. Structure your agent inputs with explicit constraints, negative prompts, and automated test checkpoints. When building tools, keep token consumption lean by caching system prompts and isolating tasks into specialized sub-agents.