Forensic audit of the user's most recent Claude Code session. Returns total spend, output ratio, duplicate file reads, idle context after auto-compact, top expensive tool calls, and an estimate of what Sipcode would have RECOVERED if optimizers were active. Use when the user asks "where did my tokens go?", "audit my last session", "why was that session so expensive?", or any forensic question about a past Claude Code session.
How to install why?
anuj7411/sipcode/why
$npx -y skills add anuj7411/sipcode --skill whyInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/anuj7411/sipcode" --skill "anuj7411/sipcode/why"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/anuj7411/sipcode" that are relevant to the current task. Run `npx skills add "https://github.com/anuj7411/sipcode"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.Jul 2026
- appinsights-instrumentationGuidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references.Jul 2026
- diagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Jul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work.Jul 2026
- golang-error-handlingIdiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single…Jul 2026
