skills/estimate-tokens/SKILL.md
This skill should be used when the user says "estimate token usage", "how many tokens am I using", "token cost of my setup", "audit token budget", "what's eating my context", "token usage breakdown", or "how expensive is my session".
npx skillsauth add kyuna0312/kyuna_token_saver Estimate TokensInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Audit and report approximate token usage across all context sources: claude.md, skills, memory files, plugins, and conversation history.
1 word ≈ 1.3 tokens
1 line of code ≈ 10-15 tokens
1KB of text ≈ 200-300 tokens
wc -w ~/.claude/CLAUDE.md 2>/dev/null || echo "No global CLAUDE.md"
wc -w ./CLAUDE.md 2>/dev/null || echo "No project CLAUDE.md"
Report: CLAUDE.md: ~[words] words ≈ [words * 1.3] tokens
find ~/.claude/plugins -name "SKILL.md" -exec wc -w {} \; 2>/dev/null | sort -rn | head -20
Sum the word counts. Multiply by 1.3 for token estimate.
wc -w ~/.claude/memory/*.md 2>/dev/null
find . -path ".remember/*.md" -exec wc -w {} \; 2>/dev/null
ls ~/.claude/plugins/ 2>/dev/null | wc -l
Each active plugin = at minimum plugin.json metadata overhead.
Output formatted breakdown:
TOKEN USAGE AUDIT
=================
claude.md (global): ~[N] tokens
claude.md (project): ~[N] tokens
Skills loaded: ~[N] tokens ([X] skills)
Memory files: ~[N] tokens
─────────────────────────────────
TOTAL CONSTANT COST: ~[N] tokens per response
Top token consumers:
1. [skill-name]: ~[N] tokens
2. [skill-name]: ~[N] tokens
3. [memory-file]: ~[N] tokens
Recommendation: [action to reduce]
Based on audit results, recommend in order:
Emit structured output as LTX rows when reporting per-source token estimates.
@v1:source|words|tokens|status
| Field | Description |
|-------|-------------|
| source | File or category (e.g. ~/.claude/CLAUDE.md, skills) |
| words | Raw word count |
| tokens | Estimated tokens (words * 1.3, rounded) |
| status | ok, warn (approaching limit), critical (over limit) |
Example:
@v1:source|words|tokens|status
~/.claude/CLAUDE.md|850|1105|critical
./CLAUDE.md|320|416|ok
skills|2400|3120|warn
references/token-benchmarks.md — Token cost benchmarks for common setupstools
This skill should be used when the user asks to "show recent changes", "show forge changelog", "show changelog for <project>", "what did I add this week", "what files did I touch today", "what packages keep recurring", "what drifts from the template", "review template suggestions", "show pending forge suggestions", "sync forge templates", "apply template suggestion", or "compute back-mapping suggestions". Provides read, drift-discovery, and template back-mapping workflows that wrap the `forge-db` MCP tools (`get_changelog`, `compute_suggestions`, `apply_suggestion`).
development
This skill should be used when the user says "build a wiki", "maintain a wiki", "ingest docs into wiki", "query my wiki", "set up llm wiki", "wiki-based knowledge base", "stop re-reading docs every session", "persistent knowledge base", or "compress my docs into wiki pages".
testing
Use this skill when the user says "/task_brain", "break down this task", "plan this", "decompose this problem", or when a task has multiple moving parts, unclear dependencies, or high ambiguity.
tools
This skill should be used when the user says "optimize settings.json", "tune settings for low tokens", "settings.json for performance", "disable auto memory", "configure for token savings", "minimal context window settings", or "settings taking too many tokens".