This is your reference guide when Claude starts burning through tokens with inefficient MCP server calls. It covers the practical stuff: adding LIMIT clauses to database queries, using compact formats for API schemas, tailing logs instead of dumping entire files, and checking context before fetching documentation you might already have. The anti-patterns table is the most useful part, showing you exactly what not to do (like SELECT * or fetching full API specs when you only need one endpoint). Think of it as a pre-flight checklist before making tool calls. If you're working with MCP servers regularly and want to keep token costs down without sacrificing quality, this will save you from the obvious mistakes.
npx skills add https://github.com/claude-dev-suite/claude-dev-suite --skill token-optimization