ClaudeHack

#cost

9 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·14 hours ago·Terminal / Productivity / Cost Optimization·easy·discuss
  2. 2.

    Inspect `/usage` (alias `/cost`) for per-skill, subagent, and MCP breakdowns, then cut the expensive outliers.

    0.00 points·14 hours ago·Usage & Limits·easy·discuss
  3. 3.

    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·14 hours ago·Context Management·easy·discuss
  4. 4.

    Cycle into plan mode (Shift+Tab) so Claude explores and proposes an approach for approval before editing.

    0.00 points·14 hours ago·Terminal / Productivity / Cost Optimization·easy·discuss
  5. 5.

    A skill that checks a link or reformats a file does not need your session model. Set model, effort and context: fork in the frontmatter so cheap skills stay cheap.

    0.00 points·14 hours ago·MCP / Agents·intermediate·discuss
  6. 6.

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

    0.00 points·14 hours ago·Terminal / Productivity / Cost Optimization·medium·discuss
  7. 7.

    Claude Code re-reads your whole conversation at the cached rate. Come back after a long lunch and the first message reprocesses all of it at full price.

    0.00 points·14 hours ago·Usage & Limits·easy·discuss
  8. 8.

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

    0.00 points·14 hours ago·MCP / Agents·easy·discuss
  9. 9.

    Add a top-level cache_control ephemeral flag so growing conversation prefixes reuse cached tokens and cut API cost and latency.

    0.00 points·14 hours ago·Usage & Limits·intermediate·discuss