npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@asifkibria/claude-code-toolkit

v2.0.0

Published

MCP server and CLI toolkit for maintaining, optimizing, and troubleshooting Claude Code installations

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

asifkibriaasifkibria

Keywords

claudeclaude-codemcpmodel-context-protocolanthropicclitoolkitmaintenanceoptimizationtroubleshootingconversationcontextsecurityprivacymcp-validatorsession-recoverytrace-managementstorage-cleanerdashboardweb-ui

Readme

Claude Code Toolkit

npm npm downloads license

Maintenance, recovery, and observability for Claude Code. CLI + MCP server + dashboard.

TL;DR — fix, monitor, manage

# 1. install
npm i -g @asifkibria/claude-code-toolkit

# 2. one-shot diagnose + fix
cct doctor                       # full integrity check (corruption, indices, oversized, orphans)
cct doctor --repair              # auto-fix everything safe
cct unstick                      # rescue a session stuck on "PDF too large" (#13518)

# 3. know your spend
cct usage                        # real token usage + cost from JSONL records
cct usage --days 7               # last week only

# 4. prevent the next break (run forever)
cct hooks scaffold auto-fix-on-start   # auto-scrub oversized content on session start
cct watch --auto-fix --daemon          # also watch live in the background

# 5. multi-account
cct profile save work            # snapshot ~/.claude.json as 'work'
cct profile switch personal      # swap accounts (auto-backup + restart Claude Code)

# 6. visual dashboard
cct dashboard                    # web UI on :1405 — Usage, Doctor, Hooks, Profiles tabs

Add it as an MCP server so Claude can do all of this from inside chat:

claude mcp add --scope user toolkit -- npx -y @asifkibria/claude-code-toolkit claude-code-toolkit-server

Then in Claude: "Run the doctor" / "Show my usage report" — or use the slash commands at docs/slash-commands.md.

What it actually does

| You have… | Run this | |---|---| | A session stuck on PDF too large / Image too large | cct unstick | | Anything weird with your install | cct doctor | | Oversized images bloating disk | cct fix | | Need to know your real API spend | cct usage (PAYG estimate — see disclaimer) | | Multiple accounts (work / personal / clients) | cct profile save/switch | | Need lifecycle automation | cct hooks list / cct hooks scaffold <id> | | A leaked secret you need to find | cct security-scan | | PII in old conversations | cct pii-scan | | A session that crashed | cct recover <id> --repair | | MCP servers that won't connect | cct mcp-validate --test |

Full command reference →

Dashboard

cct dashboard                    # opens http://localhost:1405
cct dashboard --daemon           # background
cct dashboard --stop             # stop background

21 tabs including the v2.0 additions: 💸 Usage, 🩺 Doctor, ⚙ Hooks, 👤 Profiles, 📬 Queue, plus Overview · Search · Storage · Sessions · Security · Traces · MCP · Logs · Config · Analytics · Backups · Context · Maintenance · Snapshots · Starred · About.

Cost numbers are upper-bound PAYG estimates. They do not reflect Pro/Max plan flat rates, enterprise contracts, or free credits. Use console.anthropic.com for authoritative billing.

MCP integration

Once registered (claude mcp add ...), Claude can call these tools directly: health_check, fix_image_issues, unstick_session, search_conversations, security_scan, scan_pii, audit_session, start_dashboard, and ~20 more. Full MCP tool list →

Issue #13518: "PDF too large" wedge

The cct unstick command is the dedicated fix. It scrubs the oversized base64 from the JSONL and clears the per-session warning state files that keep Claude Code in the bad state. After running it, run /clear in chat or open a new conversation to flush in-memory state.

cct install-hook makes this preventative — every session start runs cct fix quietly, so oversized content never gets a chance to wedge a session.

Links

MIT