ecc-tools-cost-audit

Trace webhook ingress and queue processing to isolate cost anomalies in ECC Tools.

1|Updated Apr 6, 2026

Search Tags:#audit #webhook #billing #cost-optimization #recursion-prevention #github-apps

Ready to run

npx skills add https://github.com/vrcms/everything-qwen-code --skill ecc-tools-cost-audit-vrcms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/vrcms/everything-qwen-code/tree/main/.qwen/skills/ecc-tools-cost-audit
Command: npx skills add https://github.com/vrcms/everything-qwen-code --skill ecc-tools-cost-audit-vrcms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses runaway costs, recursive PR creation, and billing discrepancies within the ECC Tools GitHub App environment by providing a structured, evidence-based audit workflow.

Core Features & Use Cases

Burn Path Analysis: Systematically trace webhook ingress, queue consumption, and PR generation to identify the root cause of cost spikes.
Recursion Prevention: Detect and block app-generated branches or PRs that trigger recursive analysis loops.
Use Case: If the ECC Tools app is creating duplicate PRs or exceeding usage quotas unexpectedly, use this skill to isolate the specific queue worker or webhook handler responsible for the over-consumption.

Quick Start

Use the ecc-tools-cost-audit skill to investigate the root cause of the current PR recursion and billing spike in the ECC-Tools repository.

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 audit GitHub App webhook ingress for cost spikes and billing anomalies?▼

To audit GitHub App webhook ingress for cost spikes, trace the webhook entrypoints, queue consumption, and model routing to isolate expensive execution paths. You must systematically examine worker side-effects and usage reservation logic to identify the root cause of billing discrepancies.

Why does my GitHub App create recursive PRs and how can I prevent the loop?▼

GitHub Apps create recursive PRs when app-generated branches trigger automated analysis loops. Prevent this recursion by detecting and blocking branches or PRs that originate from the app, systematically auditing queue processing and PR generation handlers to stop the cycle.

What is the best way to trace queue workers causing quota bypasses in GitHub Apps?▼

The best way to trace queue workers causing quota bypasses is to perform a burn path analysis that maps webhook ingress to queue processing and model routing. Isolating the specific worker side-effects ensures you can pinpoint and mitigate the over-consumption logic.

How do I investigate unexpected usage quota over-consumption in my automation infrastructure?▼

Investigate unexpected usage quota over-consumption by auditing usage reservation logic and tracing execution paths through webhook handlers. Systematic evidence-based auditing of queue workers and model routing isolates the specific infrastructure components responsible for the bypass.

Can I analyze webhook ingress and model routing without external dependencies?▼

Yes, you can analyze webhook ingress and model routing without external dependencies because the audit workflow operates independently. It systematically traces execution paths and worker side-effects internally to resolve cost-related anomalies and ensure safe automation.

What should I do when the ECC Tools app exceeds usage quotas unexpectedly?▼

When the app exceeds usage quotas unexpectedly, perform a structured audit to trace webhook ingress and queue consumption. Isolating the expensive execution paths and auditing worker side-effects will resolve the billing spike and prevent recursive PR generation.