Use /usage to find which MCP tools and skills burn budget

Usage & Limits·13 hours ago·verified 13 hours ago·easy·~2 min setup·verified

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

#usage #cost #mcp #limits

The problem

You hit plan limits and cannot tell whether a chatty MCP server or a recursive agent loop caused it.

The hack

After heavy sessions, run `/usage`, identify top consumers, and disable or redesign those paths.

Why it works

Anthropic added /usage specifically to make session and plan consumption visible and actionable.

Setup

1. Finish or pause a heavy session. 2. Run `/usage` (or `/cost`). 3. Note the top skill/subagent/MCP entries. 4. Disable unused MCP, tighten spawn prompts, or move rare workflows to skills—then compare next session.

Prompt

/usage

Additional details

Also watch for oversized CLAUDE.md—always-on tokens add up across a day.

Source

anthropic·View original →·by Anthropic Docs

Does this still work?

Discussion

No comments yet. Be the first to say whether this worked for you.