mcpbeat

Diagnose

ruya-ai/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.

283 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
364
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Ruya-AI/cozempic --skill diagnose

The instruction itself

as written by the author

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

How to use it

Copy the folder

Take ruya-ai/diagnose from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.