Agent skill
diagnose
Analyze Claude Code session bloat — shows token count, context usage %, and bloat breakdown. Use when the user asks about session size, context usage, or when you notice the context window is getting full.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/diagnose
SKILL.md
Run a diagnosis on the current session:
cozempic current --diagnose
The output includes:
- Weight: total session size in bytes and message count
- Tokens: exact token count (from usage data) or heuristic estimate
- Context bar: visual bar showing % of the detected context window (200K or 1M)
- Vital signs: progress ticks, file history snapshots, system reminders, thinking content, signatures, tool results
- Message type breakdown: bytes per message type
- Top 10 largest messages: biggest bloat contributors
- Estimated savings by prescription: what gentle/standard/aggressive would save
Always surface the token count and context % to the user. If context is above 60%, suggest running /cozempic:treat with a prescription recommendation:
- Under 5MB:
gentle - 5-20MB:
standard - Over 20MB:
aggressive
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?