Every token you save cuts costs and speeds up your work. This guide helps you use Claude Code efficiently without wasting tokens. You choose the right model for each task and run bash commands instead of reading files. Sonnet works best for daily coding. Opus helps with deep understanding. Following these rules saves about half your token spend.
The guide also clears up a common worry. Having many skills in your project does not waste tokens. Skills only load when needed. The real waste comes from reading large files or using verbose output. Always prefer grep, tail, or sed over reading full files. These simple steps keep your costs low and your work fast.
Global
mkdir -p ~/.claude/skills/token-efficiencyProject
mkdir -p .claude/skills/token-efficiencySource Repository
Cavemanjuliusbrussee/caveman
Talk like a smart caveman to save tokens without losing technical accuracy
Cavemanmattpocock/skills
Caveman mode for AI cuts token count 75% without losing technical accuracy
Enhance Promptgoogle-labs-code/stitch-skills
Turn vague UI ideas into clear, polished prompts with design system consistency
Humanizer Zhop7418/humanizer-zh
Remove AI writing patterns to make your text sound natural and human
Gws Modelarmorgoogleworkspace/cli
Filter harmful user content automatically with Google Model Armor for safety
Prompt Engineering Patternswshobson/agents
Master advanced prompt engineering patterns to get reliable and powerful AI outputs every time
Context Engineeringaddyosmani/agent-skills
Optimize your agent's context to improve output quality and focus
Writetw93/waza
Rewrite your prose to sound human and natural every time