ClaudeHack

#tokens

7 hacks

  1. 1.

    Use /effort (low→max) or CLAUDE_CODE_EFFORT_LEVEL so simple edits stay cheap and hard debugging gets deeper reasoning without paying max on every prompt.

    0.00 points·3 months ago·Terminal / Productivity / Cost Optimization·easy·discuss
  2. 2.

    Every installed skill spends context just being listed, before you invoke anything. Sort the list by cost, then set the ones you never use to name-only.

    0.00 points·3 months ago·Context Management·easy·discuss
  3. 3.

    Instruct Claude (and yourself) to search with rg/Glob first so giant file reads do not blow the context window.

    0.00 points·3 months ago·Terminal / Productivity / Cost Optimization·easy·discuss
  4. 4.

    Shift specialized playbooks into on-demand skills so every session does not pay for instructions you rarely need.

    0.00 points·3 months ago·Terminal / Productivity / Cost Optimization·medium·discuss
  5. 5.

    Trim project memory to under ~200 lines so Claude follows critical rules instead of drowning them in noise.

    0.00 points·3 months ago·Claude Code / CLAUDE.md·easy·discuss
  6. 6.

    Run /context to break down token consumers—CLAUDE.md, MCP tools, conversation—and prune the expensive ones.

    0.00 points·3 months ago·Context Management·easy·discuss
  7. 7.

    Turn off MCP servers unrelated to the current project—their tool schemas still consume context at session start.

    0.00 points·3 months ago·MCP / Agents·easy·discuss