ecc-tools-cost-audit

Diagnoses runaway PR creation, quota bypass, and premium-model leakage in the ECC Tools GitHub App.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill ecc-tools-cost-audit-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/ecc-tools-cost-audit
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill ecc-tools-cost-audit-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a GitHub App burns cost through recursive PR creation, usage-limit bypass, premium-model leakage, or duplicate queue jobs, this Skill provides an evidence-first audit workflow to trace the exact burn path and fix it in impact order. ## Core Features & Use Cases - Ingress-to-Worker Tracing: Maps webhook router, queue producer, queue consumer, PR creation, usage reservation, and model routing paths before theorizing about root causes. - High-Signal Burn Pattern Detection: Identifies PR multiplication, post-enqueue quota races, free-tier premium routing, retry burn, and app-generated branch recursion. - Burn-Ordered Fixes: Prioritizes fixes by cost impact (PR multiplication, quota bypass, premium leakage, duplicate fanout) with narrow verification steps. - Use Case: A customer reports the app created dozens of duplicate PRs and exceeded their usage quota. Use this Skill to trace the webhook-to-worker path, find that synchronize events re-enqueue analysis on app-owned branches, and stop the recursion. ## Quick Start Audit the ECC Tools repo to find why the GitHub App is over-creating PRs and bypassing usage limits, then report the root cause with exact file paths.

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 investigate a GitHub App that creates too many PRs?▼

Trace the webhook router and queue consumer first, then inspect PR helpers, branch naming, dedupe logic, and synchronize-event handling. If app-generated branches can re-enter analysis through pull_request.synchronize or push events, treat that as a priority-0 recursion risk.

How to detect usage quota bypass in a queue-based worker?▼

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

Why does my app spend tokens but produce no output?▼

This happens when analysis runs before persistence safety is guaranteed. If the system can spend tokens and then fail on PR creation, file update, or branch collision, it burns cost without shipping value and should be classified as burn-with-broken-output.

Can free-tier users reach premium model providers?▼

Yes, if model selection and tier branching do not gate provider routing. When premium API keys are present in the environment, free or capped queued jobs can still route into premium analyzers, causing real spend leakage even if users never see the result.

When should I not use this cost audit workflow?▼

Do not use it for generic billing reviews, repo-wide code review passes, or work outside the ECC-Tools repository. It is a focused operator workflow for webhook, queue, usage reservation, PR creation, and paid-gate enforcement paths only.