ecc-tools-cost-audit

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill ecc-tools-cost-audit-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/ecc-tools-cost-audit
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill ecc-tools-cost-audit-cyrus-pinto

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 queue jobs, engineers need a disciplined audit workflow instead of broad repo wandering. This Skill provides an evidence-first investigation path for the ECC Tools repo that separates repo-side burn root causes from customer billing impact. ## Core Features & Use Cases - Ingress-to-worker tracing: Maps webhook events through queue producers and consumers to find where expensive analysis paths converge. - High-signal burn pattern detection: Identifies PR multiplication, post-enqueue usage reservation races, free-tier premium routing, retry burn, and app-generated branch recursion. - Burn-ordered fixes and verification: Prioritizes fixes by cost impact and requires narrow proving steps 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 webhook-to-worker path, find the synchronize-event recursion on app-owned branches, fix the dedupe logic, and verify the burn path is blocked. ## Quick Start Use the ecc-tools-cost-audit skill to investigate why the ECC Tools app is creating duplicate PRs and exceeding usage quotas.

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 runaway PR creation from a GitHub App?

Trace the webhook router to the queue consumer and inspect PR helpers for missing dedupe, synchronize-event handling, and existing-PR reuse. If app-generated branches can re-enter analysis via pull_request.synchronize or push events, treat that recursion as a priority-0 burn risk.

How do I find quota bypass in a usage-gated analysis pipeline?

Compare where quota is checked against where usage is reserved or incremented. If quota is checked at enqueue time but usage is only charged inside the worker, concurrent requests can all pass the front-door gate and exceed quota.

Why is my GitHub App spending on premium models for free-tier users?

Premium-model leakage happens when model selection and tier branching let free or capped users route into premium providers whenever premium API keys are present. Inspect the model routing path and verify tier gating happens before provider selection.

When should I not use this cost audit workflow?

Do not use it for generic billing questions, repo-wide code reviews, or work outside the ECC-Tools repository. It is a focused operator workflow for webhook, queue, usage reservation, and PR creation burn paths, not a general audit skill.

How do I verify a cost burn fix actually worked?

Rerun only the targeted tests or integration slices covering the changed path, then confirm the burn path is blocked, deduped, downgraded, or rejected early. State the final status precisely as changed locally, verified locally, pushed, deployed, or still blocked.