When your GitHub App starts burning through API quota or creating recursive PRs, this is the structured audit workflow you run. It walks you through the ECC Tools repo from webhook ingress to queue workers, helping you trace whether free users are leaking into premium model paths, whether app-generated branches are re-triggering analysis, or whether usage gates are being checked before enqueue but only enforced after spend. The workflow is deliberately scoped to cost and burn, not general code quality, and it keeps you from theorizing before you've actually mapped the enqueue surface. Honest take: if you've ever had a bot PR itself into a recursion loop, you know exactly why this exists.
npx skills add https://github.com/affaan-m/everything-claude-code --skill ecc-tools-cost-audit