用于审计 ECC Tools 的成本与计费异常,快速定位滥用、泄漏与重复任务来源。
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "ecc-tools-cost-audit" 技能: 1. 下载 https://raw.githubusercontent.com/affaan-m/ECC/main/skills/ecc-tools-cost-audit/SKILL.md 2. 保存为 ~/.claude/skills/ecc-tools-cost-audit/SKILL.md 3. 装好后重载技能,告诉我可以用了
请按 evidence-first 方法审计 ECC Tools 仓库近 7 天的 PR 创建相关成本,重点检查异常高频 PR、触发来源、关联账号、时间分布,并给出可验证证据与止损建议。
一份包含异常 PR 成本来源、证据链、影响范围和处置建议的审计结论。
请审计 ECC Tools 的调用与计费记录,查找是否存在配额绕过、Premium 模型误用或泄漏。请列出可疑请求、调用路径、涉及身份、费用影响,并按置信度排序。
一份按风险等级排序的问题清单,附带证据、费用估算和修复优先级建议。
请分析 ECC Tools 仓库的作业执行与 GitHub App 相关计费,识别重复任务、重试风暴或突增成本事件。输出异常时间线、根因假设、验证依据和优化建议。
一份异常时间线和根因分析报告,说明哪些任务或应用导致了成本飙升及后续优化方案。
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:
…
通过双评审智能体对结果进行对抗式校验,提升输出发布前的可靠性
帮助核实收入、定价、退款与团队计费的真实情况并定位异常