From token-calculator
Analyze text for token count estimation and API cost calculation. Use when the user asks about tokens, costs, context window usage, or wants to optimize prompt length.
How this skill is triggered — by the user, by Claude, or both
Slash command
/token-calculator:token-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Estimate token counts and API costs for text content.
Estimate token counts and API costs for text content.
These ratios match @token-calc/core constants (TOKENIZATION_RATIOS):
charsToTokens: 0.25)charsToTokens: 0.33)| Model | Input/MTok | Output/MTok |
|---|---|---|
| Opus 4.6 | $15.00 | $75.00 |
| Sonnet 4.6 | $3.00 | $15.00 |
| Haiku 4.5 | $0.80 | $4.00 |
Note: 200K tokens is the limit per conversation, as documented publicly by Anthropic.
| Tier | Tokens | Scope |
|---|---|---|
| Claude web standard | 200K | per conversation |
| Claude API standard | 200K | per conversation |
| Claude API extended | 1M | per conversation |
Always report:
When context usage is high, suggest:
npx claudepluginhub novanoticia/token-calculator-suite --plugin token-calculatorEstimates token usage, costs across Haiku/Sonnet/Opus, complexity levels, and time for features by analyzing codebase files/lines via Glob/Read/Grep. Use for pre-implementation planning.
Tracks tokens, analyzes caching behavior, identifies bottlenecks in tool usage, and estimates costs to optimize Claude Code session performance and efficiency.
Estimates input token count and response complexity, then offers a menu to choose response depth (brief, detailed, exhaustive) before answering. Use to control token consumption in Claude Code.