Use when the user asks about token usage, session cost, or wants to check optimization effectiveness.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill token-check --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Token Check?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-token-check)More formats (shields.io, HTML) on the badges page.
---
name: token-check
description: Use when the user asks about token usage, session cost, or wants to check optimization effectiveness.
disable-model-invocation: true
allowed-tools: Bash
---
Analyze the current Claude Code session for token efficiency:
## Check These
1. **Context loaded**: What CLAUDE.md, rules, and skills are currently loaded?
2. **MCP servers**: How many tool definitions are in context?
3. **Conversation length**: How many turns deep are we?
4. **File reads**: Have we read the same file multiple times?
## Suggest
- Whether to `/compact` the conversation
- Whether to `/clear` and start fresh
- Which MCP servers to disable if unused
- Whether CLAUDE.md is too large
- Whether rules files should use path-scoping
## Output
```
Session Health Report
─────────────────────
Context usage: [estimate]
Conversation turns: [count]
Suggested action: [compact / clear / continue]
Optimization tips: [specific suggestions]
```
<!-- Skill by Huzefa Nalkheda Wala | claude-code-optimizer -->
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...