yoodongdong

Cc Waste — Development skill for Claude Code

Development community

Scans your local Claude Code session logs and generates a self-contained HTML report of token usage, cost, and likely waste (repeated file reads, oversized tool results, unused skills) — 100% local, n.

How to install Cc Waste

This entry records only its repository, not the path inside it, so there is no exact command to give. Open yoodongdong/cc-waste and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Cc Waste does

Scans your local Claude Code session logs and generates a self-contained HTML report of token usage, cost, and likely waste (repeated file reads, oversized tool results, unused skills) — 100% local, no network calls. Optional --fix auto-disables unused skills.

Alternatives in Development

  • Om Tidy — Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits ove 4.6k ★
  • Clauditor — Stop Claude Code from burning through your quota in 20 minutes 367 ★
  • Playbook — How to dispatch well — choosing flash vs pro, writing self-contained briefs, parallelism, verifying results, a 116 ★

README

cc-waste

[![npm downloads](https://img.shields.io/npm/dt/cc-waste.svg)](https://www.npmjs.com/package/cc-waste) [![npm version](https://img.shields.io/npm/v/cc-waste.svg)](https://www.npmjs.com/package/cc-waste)

Scans your local Claude Code session logs and generates a single self-contained HTML report showing token usage, estimated cost, and likely token-waste patterns — repeated file reads, oversized tool results, large pasted content, low prompt-cache hit rates, and unused or rarely-used installed skills. With `--fix`, it disables the unused/rarely-used skills itself and the report shows exactly what it found and what it did about it.

**100% local.** It only reads files under your own `~/.claude/projects/` directory. It makes no network calls and sends nothing anywhere.

**Early version.** Token/cost numbers are heuristic estimates (not exact), and this hasn't been battle-tested against every Claude Code setup yet (Windows, huge logs, etc.). Feedback and bug reports are very welcome — [open an issue](https://github.com/yoodongdong/cc-waste/issues).

Usage

npx cc-waste

This writes `cc-waste-report.html` in the current directory, prints a summary to the terminal, and **opens the report in your default browser** — no extra flag needed. If any installed skill looks unused, the terminal and the report both print the exact command to clean it up.

Options

-o, --out      Output HTML path (default: ./cc-waste-report.html)
--dir          Claude config dir to scan (default: $CLAUDE_CONFIG_DIR or ~/.claude)
--days            Only include activity from the last N days
--project    Only include projects whose folder name contains this
--json               Also write a .json file with the raw aggregated data
--no-open            Don't auto-open the report in a browser (default: opens)
--fix                Disable unused/rarely-used skills automatically (see below)
-h, --help           Show help

Examples: