ecc-tools-cost-audit

Audit GitHub App usage and billing in the ECC-Tools repository.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/ROYCE-8425/ai-marketing-hub --skill ecc-tools-cost-audit-royce-8425
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/ROYCE-8425/ai-marketing-hub/tree/main/skills/ecc-tools-cost-audit
Command: npx skills add https://github.com/ROYCE-8425/ai-marketing-hub --skill ecc-tools-cost-audit-royce-8425

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill unit "ecc-tools-cost-audit" provides a comprehensive approach to analyzing and resolving unexpected cost spikes in the ECC Tools GitHub App.

Core Features & Use Cases

  • Evidence-First Audit: Offers a systematic process for pinpointing cost drivers, including runaway PR creation, quota bypass, premium-model leakage, and duplicate jobs.
  • Targeted Workflows: Tailored for use within the ECC-Tools repo, focusing on webhook handlers, queue workers, and usage reservation logic.
  • Quick Problem Resolution: Facilitates quick resolution by separating billing impacts, root causes, and identifying product or entitlement gaps.

Quick Start

Initiate a cost audit by activating the "ecc-tools-cost-audit" Skill in the ECC-Tools GitHub 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 usage and billing for unexpected cost spikes?

Auditing GitHub App usage and billing requires analyzing webhook handlers and queue workers to identify runaway PR creation, quota bypass, and duplicate jobs causing unexpected cost spikes.

What causes excessive PR creation and duplicate jobs in repository audits?

Excessive PR creation and duplicate jobs in repository audits stem from webhook handler inefficiencies and usage reservation logic gaps, leading to unauthorized premium usage and quota bypass.

How do I identify premium-model leakage and unauthorized usage in GitHub repositories?

Identifying premium-model leakage involves repository audit techniques targeting webhook handlers and queue workers to separate billing impacts and isolate unauthorized premium usage.

Does cost analysis for the ECC-Tools repo require specific environment access?

Yes, cost analysis requires access to GitHub repository data and knowledge of ECC Tools internal logic, specifically focusing on usage reservation logic and webhook handlers.

What's the best way to resolve GitHub App billing impacts from runaway PR creation?

Resolving GitHub App billing impacts involves evidence-first workflows that separate billing impacts from root causes, identifying product or entitlement gaps to mitigate runaway PR creation.

Why does GitHub App quota bypass occur during repository cost analysis?

GitHub App quota bypass occurs during cost analysis when usage reservation logic fails to properly restrict webhook handlers and queue workers, causing duplicate jobs and unauthorized premium usage.