ecc-tools-cost-audit

原文涵盖的主题

• ECC Tools Cost Audit
• Skill Stack
• When To Use
• Scope Guardrails
• Workflow
• 1. Freeze repo scope
• 2. Trace ingress before theorizing
• 3. Trace the worker and side effects

Use this skill when the user suspects the ECC Tools GitHub App is burning cost, over-creating PRs, bypassing usage limits, or routing free users into premium analysis paths. This is a focused operator workflow for the sibling ECC-Tools repo. It is not a generic billing skill and it is not a repo-wide code review pass. Pull these ECC-native skills into the workflow when relevant: autonomous-loops for bounded multi-step audits that cross webhooks, queues, billing, and retries agentic-engineering for tracing the request path into discrete, provable units customer-billing-ops when repo behavior and customer-impact math must be separated cleanly search-first before inventing helpers or re-implementing repo-local utilities security-review when auth, usage gates, entitlements, or secrets are touched verification-loop for proving rerun safety and exact post-fix state tdd-workflow when the fix needs regression coverage in the worker, router, or billing paths user says ECC Tools burn rate, PR recursion, over-created PRs, usage-limit bypass, or premium-model leakage the task is in the sibling ECC-Tools repo and depends on webhook handlers, queue workers, usage reservation, PR creation logic,

这里只展示节选，请以完整原文和当前要求为准。