ECC Tools Cost Audit FAQs

Question 1

Does it automatically change my code?

Accepted Answer

It starts in a read-only mode to trace the ingress and worker paths, suggesting or applying fixes only when explicitly directed by the user to ensure safety.

Question 2

What is premium-model leakage in this context?

Accepted Answer

It refers to scenarios where free-tier or capped users are incorrectly routed to expensive AI models when premium keys are available, resulting in unintended spend.

Question 3

How does it handle recursive PR creation?

Accepted Answer

It inspects PR helpers and branch naming logic to detect and prevent app-generated branches from triggering new analysis loops, which is a priority-0 recursion risk.

Question 4

What is the primary focus of the ECC Tools Cost Audit skill?

Accepted Answer

It focuses on identifying and fixing operational cost spikes like runaway PR creation and token leakage within the ECC Tools GitHub App environment.

Question 5

Can this skill be used on any repository?

Accepted Answer

No, it is specifically designed for the sibling ECC-Tools repository and its unique architecture of webhooks, queues, and workers.

ECC Tools Cost Audit

Características Principales

Casos de Uso

Energy Procurement Specialist

Energy Procurement & Strategy

Canary Watch

Características Principales

Casos de Uso