ecc-tools-cost-audit

Audit runaway costs and resource usage in ECC Tools workflows.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill ecc-tools-cost-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/ecc-tools-cost-audit
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill ecc-tools-cost-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evidence-first workflow to identify and diagnose excessive spend, bursty PR creation, and billing anomalies in the ECC Tools ecosystem.

Core Features & Use Cases

  • Trace webhook, queue, and PR paths to isolate burn causes.
  • Separate quota usage, premium-model leakage, and duplicate-job scenarios for precise costing.
  • Provide a repeatable audit workflow with guardrails and clear remediation steps for the ECC Tools repo.
  • Use Case: when the app spikes in PRs or cost, run the workflow to quantify impact and guide fixes.

Quick Start

Run the ECC Tools cost audit workflow against the ECC Tools repository to begin tracing burn paths and cost anomalies.

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 runaway costs and billing anomalies in a GitHub App workflow?

To audit runaway costs in a GitHub App workflow, trace webhook handlers, queue workers, and PR creation logic to isolate burn causes and quantify billing anomalies. This process separates quota usage, premium-model leakage, and duplicate-job scenarios to provide a structured burn analysis.

How do I trace webhook handlers and queue workers to isolate burn causes?

Trace webhook handlers and queue workers by analyzing PR creation logic and usage paths to isolate burn causes. This workflow separates quota bypass, premium-model leakage, and duplicate-job scenarios to produce a structured burn analysis with clear remediation steps.

Can I use this cost audit workflow to diagnose duplicate-job scenarios and quota bypass?

Yes, you can use this cost audit workflow to diagnose duplicate-job scenarios and quota bypass. It traces usage and billing paths to separate these specific scenarios, enabling precise costing and providing guardrails with remediation steps for the repository.

What's the best way to analyze PR churn and resource usage in ECC Tools?

The best way to analyze PR churn and resource usage is running an evidence-first audit workflow that traces webhook and PR paths. This approach isolates burn causes, separates quota usage from premium-model leakage, and outputs a structured burn analysis to guide fixes.

Why does my GitHub App spike in PR creation and cost without warning?

Your GitHub App spikes in PR creation and cost due to bursty PR creation, quota bypass, or premium-model leakage within webhook and queue worker paths. Running a cost audit workflow quantifies the impact of these billing anomalies and guides remediation.