When using Claude Opus 4.6, the cost is usually not because you “ask too many questions,” but because “the context is too long and the output is too verbose.” If you ask the same question in a shorter, more focused way, your quota consumption will drop noticeably. The following approach requires no extra tools and can be applied directly in everyday conversations.
First, remember one thing: Claude Opus 4.6 mainly spends tokens on input and output
Claude Opus 4.6 counts both what you send and what it replies as consumption, especially in long conversations that repeatedly carry historical context. The more you treat chat as a “long-term memo,” the more expensive each message becomes. The core of saving money is to reduce ineffective history and reduce useless long-form output.
Align the goal before asking: Use “confirmation questions” instead of writing long prompts right away
Let Claude Opus 4.6 first give you a brief plan or outline, then decide whether to expand—this is usually cheaper than having it write everything in one go. For example, say “Give me 3 approaches + the risks of each, no more than 80 Chinese characters per item.” After confirming the direction, have it expand only one of them. This avoids it writing a long section that you won’t use at all.
Control context length: Don’t let old chat drag new questions along
If you discuss the same topic for a long time, Claude Opus 4.6 will pull more and more history into the calculation, and the cost will rise. A cheaper approach is: periodically summarize once—have it compress the context into 10 bullet points—then start a new chat and paste only this summary. When you need to reference old information, explicitly specify “use only the material I paste below,” to keep it from going back and scanning the entire record.
Handling attachments and long texts: Extract first, then analyze—don’t feed the whole thing directly
Throwing an entire PDF/long article directly to Claude Opus 4.6 can easily result in “reading a lot but using very little.” A more reliable method is to have it first tell you which sections it needs (page numbers, headings, keywords), and then you paste the relevant excerpts. If you must upload it, you can also ask Claude Opus 4.6 to produce only a “key information extraction table” first; after confirming the fields, proceed to deeper analysis.
Limit the output format: Turn off the “urge to answer at length”
Setting a clear upper limit for Claude Opus 4.6 is crucial, such as “max 200 words,” “output tables only,” or “one sentence per item.” If you only need the conclusion, say “Give the conclusion first + 3 supporting points, no process,” which usually saves a large chunk of output. The same applies to writing code or copy: ask for the minimum viable version first, then add as needed—don’t chase a “perfect long draft” in one shot.
