claude-prospector

Solid

Claude Code efficiency and hygiene toolkit — token spend analysis across the 5h / 7d / Sonnet-7d billing windows plus configuration overlap auditing. Ships as a Claude Code plugin with three skills (usage-analysis, usage-dashboard, claude-audit) backed by a Python CLI.

plugin 1 stars 1 forks Updated 3 days ago MIT

Install

Plugins install via a marketplace, in two steps.

This plugin isn't listed in a marketplace we've indexed. Install it directly from its GitHub repository — the README has the setup steps.

View on GitHub

Bundles

Everything this plugin ships — skills, agents, commands, hooks, and MCP servers it bundles.

Skills (5)

AI & Automation Listed

claude-audit

Audit a project's effective Claude Code configuration — custom and plugin-provided agents and skills — and produce a structured overlap/conflict report with keep / modify / drop recommendations scoped to the project's stated objectives. Trigger this skill whenever the user types `/claude-audit`, asks to "audit my claude config", "find overlap in my agents", "check for skill conflicts", "are any of my agents duplicates", "what's redundant in my setup", or any similar request to review the agent/skill surface for the current project. Also trigger after a fresh plugin install when the user wants to verify nothing new collides with what's already there.

1 Updated 3 days ago
glitchwerks
AI & Automation Listed

session-analysis

Use when the user wants a judgment-level read on whether a Claude Code session stayed on task — did the agent do what was originally asked, and what did it acknowledge skipping. This is the interpretive (LLM) complement to the deterministic `session-audit` CLI: 1a extracts ask-vs-done for free; this skill adds the `Variance` and `What was NOT done` judgment that a parser can't compute, then persists a combined record for drift analysis. Cost: ~1-3k tokens of the current session, paid only when invoked. Opt-in by design — run it selectively, not on every session. Best run in a Sonnet (or stronger) session; the judgment quality depends on it. Use `session-audit` (CLI) for the free deterministic ask/actions extract. Use `usage-analysis` for token-spend insights. Use `claude-audit` for agent/skill config overlap. Use THIS skill for "did this session drift from what I asked". Trigger phrases: "/session-analysis", "did this session stay on task", "analyze session drift", "did the agent do what I asked", "what did t

1 Updated 3 days ago
glitchwerks
Testing & QA Listed

setup-prospector

Set up claude-prospector's plugin-owned Python venv. Invoked via /setup-prospector or natural-language triggers: "set up claude-prospector", "install prospector dependencies", "prospector isn't working", "fix prospector", "repair prospector". Do not trigger on "dashboard", "usage analysis", or "skill adoption" — those are distinct skills.

1 Updated 3 days ago
glitchwerks
Code & Development Listed

usage-analysis

Use when the user asks an interpretive question about their Claude Code token spend — what's interesting, what's anomalous, what to change. This skill produces insights and questions; it does NOT enumerate top consumers (the dashboard does that). Use `usage-dashboard` for "show me the numbers." Use `claude-audit` for "audit my config overlap." Use this skill for "tell me what's interesting / what should I change." Trigger phrases: "am I close to my Claude limit", "how much Sonnet am I using", "where are my Claude tokens going", "what's eating my Claude budget", "why is my Claude spend so high", "what should I change about my Claude setup".

1 Updated 3 days ago
glitchwerks
Data & Documents Listed

usage-dashboard

Use when the user explicitly asks to regenerate, rebuild, or refresh the `claude-prospector` token-usage dashboard with no interpretive question attached — runs `python -m claude_prospector dashboard`, writes the HTML file, and reports the output path. Do NOT use when the user is asking what the data means, where their budget stands, or what to change (use `usage-analysis` instead — it regenerates as part of answering). Trigger phrases: "regenerate the usage dashboard", "rebuild my claude-prospector dashboard", "refresh the token dashboard", "regen the prospector dashboard".

1 Updated 3 days ago
glitchwerks

Hooks (6)

.gitkeep check-prospector-setup.py dashboard-regen.py hooks.json lib skill-tracker.py

Quality Score: 66/100

Stars 20%
10
Recency 20%
100
Manifest 20%
100
Documentation 15%
0
Issue Health 10%
50
License 10%
100
Description 5%
100

Details

Author
glitchwerks
Repository
glitchwerks/claude-prospector
Created
2 months ago
Last Updated
3 days ago
Language
Python
License
MIT