Evidence-first ECC Tools burn and billing audit workflow. Use when investigating runaway PR creation, quota bypass, premium-model leakage, duplicate jobs, or GitHub App cost spikes in the ECC Tools repo.
The ecc-tools-cost-audit skill provides an evidence-first workflow for investigating abnormal cost generation, billing inconsistencies, and runaway automation behavior inside the ECC-Tools GitHub App ecosystem. It is designed specifically for audits involving excessive pull request creation, quota bypass scenarios, premium-model leakage, duplicate queue jobs, and recursive analysis loops that can increase operational spend. The workflow emphasizes provable tracing over assumptions by requiring operators to inspect queue ingress, webhook routing, worker execution, billing paths, and model routing before proposing fixes. It also separates repository-side burn causes from customer-facing billing impact and product entitlement gaps to avoid conflating operational issues with account or subscription behavior.
The skill includes a structured audit process that starts with freezing repository scope and identifying the exact system surface under investigation, such as webhook routers, queue consumers, PR creation logic, or usage reservation paths. It supports multi-step tracing across asynchronous workflows and integrates with related ECC-native skills for verification, security review, regression testing, and billing analysis when needed. The workflow specifically highlights high-risk cost patterns including PR multiplication, retry-driven burn, quota race conditions, and premium-model access leakage. It also focuses on identifying scenarios where analysis consumes resources without successfully persisting usable output, classifying these as burn-with-broken-output conditions.
This skill is intended for operators, maintainers, platform engineers, and incident responders working within the ECC-Tools repository. It is most useful when customer reports indicate incorrect billing, excessive automated PR generation, or suspicious analysis behavior tied to webhook events or queue processing. The workflow is intentionally scoped to the sibling ECC-Tools repository and is not intended for general billing investigations or broad repository-wide code reviews.
Use this skill when investigating suspected ECC-Tools GitHub App cost spikes, runaway PR creation, quota bypass behavior, premium-model leakage, duplicate analysis jobs, or billing inconsistencies tied to analysis workflows.
No. The workflow starts in a read-only investigation mode unless the user explicitly requests code or configuration changes.
The audit focuses on webhook handlers, queue producers and consumers, PR creation paths, usage reservation and billing logic, model routing behavior, and retry or synchronization flows within the ECC-Tools repository.
No. The workflow is intentionally scoped to ECC-Tools operational burn analysis and should not be used as a generic billing, checkout, or UI troubleshooting process.
The workflow is designed to detect recursion through app-generated branches or PRs, quota race conditions, premium-model access leakage, duplicate queue execution, retry-driven cost amplification, and token burn without usable persisted output.
Quick Setup:
.claude/skills/Repository
affaan-m/everything-claude-code