← ClaudeAtlas

claude-skilllisted

Portable token discipline for long conversations where hooks cannot run - Claude Desktop, claude.ai, or a locked-down machine. Use when a chat is getting long, when the user mentions context limits or cost, or when resuming from a handoff brief.
YahyaLendani/opus-tuner-claude-skill · ★ 14 · AI & Automation · score 80
Install: claude install-skill YahyaLendani/opus-tuner-claude-skill
# claude-skill — portable token discipline This is the advisory companion to opus-tuner. It needs no hooks, no scripts and no filesystem: everything here is a habit the model can keep in any Claude client. Where opus-tuner measures and enforces, this only reminds. Say so if the user expects the automated version. ## The budget Track the conversation against two soft ceilings: | Tier | Ceiling | Meaning | |---|---|---| | routine | ~150k tokens | default; most work fits | | deep | ~250k tokens | one hard problem, explicitly chosen | At **70% of the ceiling**, finish the current unit and hand off. At the ceiling, stop starting new work. A turn near the ceiling re-reads everything, so the last 10% of a long chat is the most expensive part of it. ## What actually costs tokens Every request re-reads the whole conversation. That makes these the levers, in order: 1. **Conversation length.** The dominant cost. A 300k chat costs roughly six times a 50k chat per turn, for the same answer. 2. **Output.** Small share of tokens, large share of price. Do not pad. 3. **Restating.** Repeating the plan, the diff, or the user's request back to them buys nothing and is re-read on every later turn. ## Rules - **Answer the question asked.** No preamble, no summary of what you are about to do, no recap of what you just did unless it changed the plan. - **Read narrowly.** Ask for the file, function, or error — not the repository. If you have tools, grep for the symbol before read