Menu
Evidence-first ECC Tools burn and billing audit workflow. Use when investigating runaway PR creation, quota bypass, premium-model leakage, duplicate jobs, or GitHub App cost spikes in the ECC Tools repo.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.
Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.
| name | ecc-tools-cost-audit |
| description | Evidence-first ECC Tools burn and billing audit workflow. Use when investigating runaway PR creation, quota bypass, premium-model leakage, duplicate jobs, or GitHub App cost spikes in the ECC Tools repo. |
| origin | ECC |
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 retriesagentic-engineering for tracing the request path into discrete, provable unitscustomer-billing-ops when repo behavior and customer-impact math must be separated cleanlysearch-first before inventing helpers or re-implementing repo-local utilitiessecurity-review when auth, usage gates, entitlements, or secrets are touchedverification-loop for proving rerun safety and exact post-fix statetdd-workflow when the fix needs regression coverage in the worker, router, or billing pathsECC-Tools repo and depends on webhook handlers, queue workers, usage reservation, PR creation logic, or paid-gate enforcementECC-Tools repo, not in everything-claude-codeECC-Tools reposrc/index.* or the main entrypoint firstIf the user asked for code changes, prioritize fixes in this order:
Keep the pass bounded to one to three direct fixes unless the same root cause clearly spans multiple files.
If pushes, PR syncs, and manual audits all enqueue the same job and the worker always creates a PR, analysis equals PR spam.
If usage is checked at the front door but only incremented in the worker, concurrent requests can all pass the gate and exceed quota.
If free queued jobs can still route into Anthropic or another premium provider when keys exist, that is real spend leakage even if the user never sees the premium result.
If pull_request.synchronize, branch pushes, or comment-triggered runs fire on app-owned branches, the app can recursively analyze its own output.
If the system can spend tokens and then fail on PR creation, file update, or branch collision, it is burning cost without shipping value.