ecc-tools-cost-audit

Trace webhook and queue events to audit cost burn in ECC Tools workflows.

2|Updated Mar 3, 2026

Search Tags:#audit #observability #billing #github-app #ecc-tools #cost-burn

Ready to run

npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill ecc-tools-cost-audit-momodaviluke

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ecc-tools-cost-audit
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.agents/skills/ecc/ecc-tools-cost-audit
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill ecc-tools-cost-audit-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ECC Tools cost audit workflow focuses on surfacing and validating cost anomalies within the ECC Tools ecosystem, enabling teams to detect runaway billing paths such as excessive PR creation, quota bypass, or premium-model leakage, and to take accountable corrective actions.

Core Features & Use Cases

Evidence-driven tracing: map webhook, queue, and worker paths to identify high-burn scenarios and exact surface points.
Burn-path isolation: detect PR multiplication, quota bypass, and premium leakage to prevent repeat incidents.
Guardrails & remediation: provide clear steps for containment, verification, and regression-safe fixes with documented success criteria.

Quick Start

Run a read-only audit on the ECC Tools repository to surface high-burn paths and establish a baseline.

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 cost burn from excessive PR creation in GitHub workflows?▼

To audit cost burn from excessive PR creation, trace webhook handlers and queue workers to identify high-burn scenarios. This process maps events to exact surface points, isolating PR multiplication and preventing repeat billing incidents using evidence-driven tracing.

What causes premium-model leakage and quota bypass in repository workflows?▼

Premium-model leakage and quota bypass occur when premium path routing across PRs and branches misroutes requests. Burn-path isolation detects this leakage by tracing usage reservations and worker paths, preventing unauthorized premium feature consumption.

Can I run a read-only analysis on webhook handlers without affecting active queues?▼

Yes, you can run a read-only analysis on webhook handlers without affecting active queues. Deterministic multi-step tracing ensures read-only analysis validates anomalies safely, establishing a baseline without altering live workflow states.

How do I remediate billing spikes and ensure regression-safe fixes?▼

To remediate billing spikes and ensure regression-safe fixes, apply documented guardrails for containment and rerun safety. This provides clear steps for verification and regression-safe fixes with documented success criteria to prevent future anomalies.

When should I use multi-step tracing for cost audit instead of standard billing alerts?▼

Use multi-step tracing for cost audit when standard billing alerts cannot pinpoint exact surface points. Multi-step tracing maps webhook, queue, and worker paths to isolate root causes of high-burn scenarios, exceeding standard alert capabilities.