Verified:GitHub

ecc-tools-cost-audit

Trace webhook ingress through queue workers to diagnose cost burn in the ECC Tools GitHub App.

Updated Sep 13, 2025

Search Tags:#github app #cost audit #queue workers #pr recursion #usage throttling #premium model routing #billing verification

Ready to run

npx skills add https://github.com/llmh333/employee_management_spring --skill ecc-tools-cost-audit-llmh333

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/ecc-tools-cost-audit
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill ecc-tools-cost-audit-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify why the ECC Tools GitHub App is generating runaway work and costing more than expected, then guides you to verify the fix is actually stopping the burn.

Core Features & Use Cases

Evidence-first burn diagnosis: Traces the webhook/queue/worker/model routing chain to pinpoint where PR multiplication, quota bypass, or premium-model leakage is happening.
Recursion and fanout detection: Treats app-generated branches and PRs as potential feedback loops and prioritizes stopping PR recursion first.
Ordered remediation and proof: Recommends a burn-impact-based fix order and requires the smallest proving rerun steps to confirm the final status precisely.

Quick Start

Use the ecc-tools-cost-audit skill to investigate the ECC Tools repo after reports of excessive PR creation, duplicate jobs, or unexpected premium/billing spend.

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 diagnose unexpected cost burn from a GitHub App creating too many PRs?▼

To diagnose cost burn from a GitHub App creating excessive PRs, trace the webhook ingress through queue workers to PR creation and model routing. This investigation pinpoints where PR multiplication, quota bypass, or premium-model leakage is happening.

What causes premium model routing leakage for free or capped users?▼

Premium model routing leakage for free or capped users occurs when the usage reservation behavior fails. Tracing the webhook and queue worker chain reveals why premium analyzers are being incorrectly routed to users who should be blocked or downgraded.

How do I fix PR recursion and duplicate job fanout in a webhook queue?▼

Fix PR recursion and duplicate job fanout in a webhook queue by treating app-generated branches as feedback loops. Prioritize stopping PR recursion first, then apply an ordered remediation to deduplicate jobs and block the burn path early.

How can I verify that usage throttling and quota bypass fixes are working?▼

Verify usage throttling and quota bypass fixes by running minimal rerun steps. These proving steps confirm the burn path is blocked, deduped, downgraded, or rejected early, ensuring the race condition and billing verification issues are resolved.

Why does retry burn happen during webhook ingress processing?▼

Retry burn during webhook ingress processing happens when queue workers repeatedly attempt failed jobs. Tracing the worker chain exposes the duplicate job fanout and retry loops causing the runaway work and unexpected billing spend.