Show full session token usage, costs, TLDR savings, and hook activity
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill tldr-stats
Show a beautiful dashboard with token usage, actual API costs, TLDR savings, and hook activity.
IMPORTANT: Run the script AND display the output to the user.
python3 $CLAUDE_PROJECT_DIR/.claude/scripts/tldr_stats.py
╔══════════════════════════════════════════════════════════════╗
║ 📊 Session Stats ║
╚══════════════════════════════════════════════════════════════╝
You've spent $96.52 this session
Tokens Used
1.2M sent to Claude
416.3K received back
97.8K from prompt cache (8% reused)
TLDR Savings
You sent: 1.2M
Without TLDR: 2.5M
💰 TLDR saved you ~$18.83
(Without TLDR: $115.35 → With TLDR: $96.52)
File reads: 1.3M → 20.9K █████████░ 98% smaller
TLDR Cache
Re-reading the same file? TLDR remembers it.
█████░░░░░░░░░░ 37% cache hits
(35 reused / 60 parsed fresh)
Hooks: 553 calls (✓ all ok)
History: █▃▄ ▇▃▇▆ avg 84% compression
Daemon: 24m up │ 3 sessions
| Metric | What it means |
|--------|---------------|
| You've spent | Actual $ spent on Claude API this session |
| You sent / Without TLDR | Actual tokens vs what it would have been |
| TLDR saved you | Money saved by compressing file reads |
| File reads X → Y | Raw file tokens compressed to TLDR summary |
| Cache hits | How often TLDR reuses parsed file results |
| History sparkline | Compression % over recent sessions (█ = high) |
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take parcadei/tldr-stats from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.