Compress heavy context before it costs tokens. Use when the user attaches or asks to read a PDF, scanned document, screenshot/large image, or a verbose log / build output / CI output — convert PDFs to Markdown, compress oversized images, and digest noisy logs so the same content costs a fraction of the tokens.
Preserve prompt-prefix stability so the provider's KV cache keeps hitting, cutting cost and latency on long sessions. Use when structuring system prompts, memory files, or tool definitions, when a long session is getting expensive, or when deciding where to put changing vs stable content.
Keep the main conversation cheap by offloading heavy sub-tasks to isolated subagent contexts. Use when a sub-task (research sweep, large-file investigation, log triage, broad search) will generate a lot of intermediate output whose conclusion is small — branch it to a subagent so the verbose work never enters the main thread, and merge back only a compact digest.
Find code by symbol name instead of reading whole files. Use when you need to locate a function, class, or method, understand where something is defined, or navigate an unfamiliar repo — query the jusTokenMax code index to get file:line + signature in a few tokens, then read only that range.
Cut the tokens the agent WRITES, not just what it reads. Activate when the user asks for terse/concise/brief output, says responses are too long, wants to save output tokens or cost, or runs /justokenmax:terse — then answer in a compressed style that preserves all technical substance while dropping filler.