.claude/skills/token-report/SKILL.md
Show a Claude Code usage report — model token breakdown, estimated costs, top projects, and session patterns. Delegates to the stats-analyzer subagent (Haiku) to avoid polluting the main context with raw data.
npx skillsauth add guidodinello/claude-dotfiles token-reportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Delegate to the stats-analyzer subagent to generate the usage report.
Do not run any analysis yourself. Do not explain what you're about to do. Invoke the subagent immediately and present its output as-is.
After presenting the report, offer one line: "Want me to dig into any of these areas further?"
development
Writes React components without unnecessary useEffect. Use when creating/reviewing React components, refactoring effects, or when code uses useEffect to transform data or handle events.
development
Use this skill whenever the user wants to write, refine, or break down a subtask for a software ticket — especially backend endpoints, frontend components, or API integrations. Trigger when the user shares a user story, acceptance criteria, or ticket scope and asks for a subtask, refinement card, or implementation breakdown. Also trigger when the user says things like "help me refine this", "write a subtask for X", "break this down", or "create a card for the endpoint / component / feature". This skill produces structured, audience-appropriate subtask write-ups for developers, PMs, and QAs alike.
development
Run the full quality pipeline (type-check, linting, tests) via the quality-checker subagent. Returns a concise summary of issues without flooding the main context with raw output.
development
Perform a HIPAA Security Rule compliance audit on a healthcare codebase. Use this skill whenever the user asks for a HIPAA audit, PHI compliance review, security review of a healthcare app, production readiness check of a patient-facing system, or wants to find where protected health information is exposed or mishandled. Also trigger when the user asks about ePHI risks, BAA coverage, audit trail gaps, or access control issues in medical software. Do not wait for the user to say "HIPAA" explicitly — trigger whenever the codebase clearly handles patient data and a security or compliance concern is raised.