ecc-tools-cost-audit

Trace cost burn root causes in ECC Tools GitHub App code.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill ecc-tools-cost-audit-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/ecc-tools-cost-audit
Command: npx skills add https://github.com/luongldptit/move-ticket --skill ecc-tools-cost-audit-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the time-consuming, ad-hoc process of tracing unexpected cost spikes in the ECC Tools GitHub App, which often stem from hidden burn paths like runaway PR creation, quota bypass, or premium model leakage that are hard to locate across webhook, queue, and billing code.

Core Features & Use Cases

  • Focused ECC-Native Audit Workflow: Tailored exclusively for the sibling ECC-Tools repository, avoiding generic billing checks that miss repo-specific burn paths.
  • Structured Burn Path Tracing: Guides step-by-step inspection of webhook routers, queue workers, PR creation logic, and usage reservation code to identify root causes of overspend.
  • Impact Separation: Explicitly separates repo-side code issues, customer billing impact, and product entitlement gaps to avoid conflating technical fixes with customer-facing remediation.
  • Use Case: A customer reports being charged for 50 unused PRs created by the ECC Tools app; this skill guides a targeted audit to trace the PR multiplication bug, quantify billing impact, and prioritize fixes by burn severity.

Quick Start

Use the ecc-tools-cost-audit skill to investigate unexpected cost spikes or excessive PR creation in the ECC Tools GitHub App.

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 unexpected GitHub App billing spikes from runaway PR creation?

To audit unexpected GitHub App billing spikes from runaway PR creation, trace webhook handlers, queue workers, and PR creation paths to identify root causes of overspend. This structured workflow separates repo-side code issues from customer billing impact.

What causes quota bypass and premium model leakage in ECC Tools billing?

Quota bypass and premium model leakage in ECC Tools billing stem from hidden burn paths across webhook routers, queue workers, and paid-gate enforcement code. An evidence-first audit scopes these product entitlement gaps without mutating unrelated code.

How do I trace ECC Tools customer billing impact for unused PR creation charges?

Trace ECC Tools customer billing impact for unused PR charges by auditing usage reservation logic and PR creation paths. This process quantifies the billing impact and prioritizes fixes by burn severity to remediate customer-facing charges.

Can I investigate ECC Tools cost burn without modifying unrelated webhook and queue worker code?

You can investigate ECC Tools cost burn without modifying unrelated webhook and queue worker code by using an evidence-first, scoped audit workflow. It strictly separates repo-side burn causes, customer billing impact, and entitlement gaps.

When do I need a structured cost audit workflow for a GitHub App?

You need a structured cost audit workflow for a GitHub App when tracing hidden burn paths like runaway PR creation, quota bypass, or premium model leakage that are hard to locate across webhook, queue, and billing code.

What is the best way to separate technical burn causes from product entitlement gaps during a billing audit?

The best way to separate technical burn causes from product entitlement gaps during a billing audit is applying a scoped workflow that isolates repo-side code issues, customer billing impact, and paid-gate enforcement failures independently.