ecc-tools-cost-audit

Audits GitHub App webhook, queue, and billing paths to trace runaway PR creation and cost burn.

Updated May 19, 2026
One-click install
npx skills add https://github.com/azusagasaku/--claude-config --skill ecc-tools-cost-audit-azusagasaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/azusagasaku/--claude-config/tree/main/skills/ecc/ecc-tools-cost-audit
Command: npx skills add https://github.com/azusagasaku/--claude-config --skill ecc-tools-cost-audit-azusagasaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a GitHub App starts burning money through runaway PR creation, quota bypass, premium-model leakage, or duplicate job retries, this Skill provides an evidence-first operator workflow to trace the exact code path responsible and fix the highest-burn issue first. ## Core Features & Use Cases - Ingress-to-Worker Tracing: Maps webhook events through queue producers and consumers to find where expensive analysis paths converge. - Burn Pattern Detection: Identifies PR multiplication, post-enqueue quota races, free-tier premium routing, retry burn, and app-generated branch recursion. - Prioritized Fixing: Orders fixes by burn impact and verifies each with the smallest proving test before claiming resolution. - Use Case: A customer reports the app created dozens of duplicate PRs and exceeded their usage quota. Use this Skill to trace the synchronize-event handler, find the missing dedupe check, and verify the fix with a targeted integration test. ## Quick Start Audit the ECC-Tools repo to find why the GitHub App is creating duplicate PRs and bypassing usage limits.

Frequently Asked Questions about ecc-tools-cost-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find why a GitHub App is creating too many PRs?▼

Trace the webhook router to the queue consumer and inspect PR creation helpers for missing dedupe, synchronize-event handling, and existing-PR reuse. Check whether app-generated branches re-enter the webhook, which causes recursive PR spam.

How to audit quota bypass in a usage-based billing system?▼

Compare where quota is checked versus where usage is reserved or incremented. If quota is checked before enqueue but charged inside the worker, concurrent requests can all pass the gate and exceed quota in a real race condition.

Why are free-tier users hitting premium AI models?▼

Premium-model leakage happens when model selection and tier branching do not gate provider routing. If free queued jobs route into premium providers whenever API keys exist, that is real spend leakage even if users never see the result.

Can this audit workflow push fixes to production automatically?▼

No. The workflow starts read-only unless a fix is explicitly requested, and it never pushes or deploys unless the user asks. Final status reporting distinguishes local changes, verification, push, and deployment.

When should I not use a cost audit workflow?▼

Do not use it for generic billing questions or repo-wide code reviews. It is a focused operator workflow for a specific GitHub App repo covering webhooks, queues, usage reservation, PR creation, and paid-gate enforcement.