Best fit
- 证据优先的ECC工具燃烧和计费审计工作流。用于调查ECC工具仓库中的失控PR创建、配额绕过、高级模型泄漏、重复作业或GitHub App成本激增。
affaan-m/ECC
ecc-tools-cost-audit
证据优先的ECC工具燃烧和计费审计工作流。用于调查ECC工具仓库中的失控PR创建、配额绕过、高级模型泄漏、重复作业或GitHub App成本激增。
74Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/ecc-tools-cost-audit"Automated source guide
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Turn ecc-tools-cost-audit's source instructions into a guide you can follow
According to the pinned SKILL.md from affaan-m/ECC: 当用户怀疑 ECC Tools GitHub App 正在消耗成本、过度创建 PR、绕过使用限制，或将免费用户引导至付费分析路径时，使用此技能。
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/ecc-tools-cost-audit"Bring this context
- A concrete task that matches the documented purpose of ecc-tools-cost-audit.
- The files, examples, or context the task depends on.
- Your constraints, target environment, and definition of done.
Expected outputs
- A result that follows the pinned ecc-tools-cost-audit instructions.
- A concise record of assumptions, inputs used, and unresolved questions.
- A final check against the source workflow and relevant permission signals.
Key source sections
Read ecc-tools-cost-audit through these 5 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
技能栈
在相关情况下，将这些 ECC 原生技能拉入工作流：
autonomous-loops 用于跨 webhook、队列、计费和重试的有界多步骤审计agentic-engineering 用于将请求路径追踪为离散的、可证明的单元customer-billing-ops 当需要清晰分离仓库行为和客户影响计算时
使用时机
用户提及 ECC Tools 消耗率、PR 递归、过度创建的 PR、使用限制绕过或付费模型泄漏 任务位于兄弟仓库 ECC-Tools 中，并依赖于 webhook 处理器、队列 worker、使用预留、PR 创建逻辑或付费网关强制执行 客户报告称应用创建了过多 PR、计费错误，或分析了代码但未产生可用结果
用户提及 ECC Tools 消耗率、PR 递归、过度创建的 PR、使用限制绕过或付费模型泄漏任务位于兄弟仓库 ECC-Tools 中，并依赖于 webhook 处理器、队列 worker、使用预留、PR 创建逻辑或付费网关强制执行客户报告称应用创建了过多 PR、计费错误，或分析了代码但未产生可用结果
范围约束
在兄弟仓库 ECC-Tools 中工作，而非 everything-claude-code 除非用户明确要求修复，否则以只读方式开始 在追踪分析消耗时，不要修改无关的计费、结账或 UI 流程 将应用生成的分支和应用生成的 PR 视为红旗递归路径，除非被证明并非如此 明确区分三件事： 仓库侧消耗的根本原因 面向客户的计费影响 需要纳入待办事项跟踪的产品或授权缺口
在兄弟仓库 ECC-Tools 中工作，而非 everything-claude-code除非用户明确要求修复，否则以只读方式开始在追踪分析消耗时，不要修改无关的计费、结账或 UI 流程
工作流
切换到兄弟仓库 ECC-Tools 首先检查分支和本地差异 确定审计的具体范围： webhook 路由器 队列生产者 队列消费者 PR 创建路径 使用预留 / 计费路径 模型路由路径
切换到兄弟仓库 ECC-Tools首先检查分支和本地差异确定审计的具体范围：
1. 冻结仓库范围
切换到兄弟仓库 ECC-Tools 首先检查分支和本地差异 确定审计的具体范围： webhook 路由器 队列生产者 队列消费者 PR 创建路径 使用预留 / 计费路径 模型路由路径
切换到兄弟仓库 ECC-Tools首先检查分支和本地差异确定审计的具体范围：
SkillSignal prompt templates
Provide the task, context, and acceptance criteria
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Task-start prompt
Confirm source fit, inputs, and outputs before acting.
Use ecc-tools-cost-audit to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.
Source-guided execution
Make the Agent explicitly follow the key extracted sections.
Apply the pinned ecc-tools-cost-audit source to [task]. Pay particular attention to these source sections: “技能栈”, “使用时机”, “范围约束”, “工作流”, “1. 冻结仓库范围”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].
Result-review prompt
Check omissions, permissions, and source drift before delivery.
Review the current ecc-tools-cost-audit result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.
Output checklist
Verify each item before delivery
The task matches the purpose documented in the SKILL.md.
The source section “技能栈” has been checked.
The source section “使用时机” has been checked.
The source section “范围约束” has been checked.
The source section “工作流” has been checked.
Inputs, constraints, and acceptance criteria are explicit.
Unverified facts, compatibility, and outcome claims are clearly marked.
Any file, command, network, or data action has been reviewed.
Choose a different workflow
When another Skill is the better fit
ecc-tools-cost-audit
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.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailchurn-prevention
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
What does ecc-tools-cost-audit do?
当用户怀疑 ECC Tools GitHub App 正在消耗成本、过度创建 PR、绕过使用限制，或将免费用户引导至付费分析路径时，使用此技能。
How do I start using ecc-tools-cost-audit?
The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/ecc-tools-cost-audit". Inspect the command and pinned source before running it.
Which Agent platforms does it declare?
No dedicated Agent platform is declared in the pinned source record.
Repository stars
234,327
Repository forks
35,711
Quality
74/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation20/30
Specificity14/25
Maintenance20/20
Trust signals20/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
ecc-tools-cost-audit by affaan-m
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.
ab-testing by coreyhaines31
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
churn-prevention by coreyhaines31
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
design-intelligence by event4u-app
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
design-system-capture by event4u-app
Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min
ECC 工具成本审计
当用户怀疑 ECC Tools GitHub App 正在消耗成本、过度创建 PR、绕过使用限制，或将免费用户引导至付费分析路径时，使用此技能。
这是一个针对兄弟仓库 ECC-Tools 的聚焦操作者工作流。它不是通用的计费技能，也不是仓库范围的代码审查。
技能栈
在相关情况下，将这些 ECC 原生技能拉入工作流：
autonomous-loops用于跨 webhook、队列、计费和重试的有界多步骤审计agentic-engineering用于将请求路径追踪为离散的、可证明的单元customer-billing-ops当需要清晰分离仓库行为和客户影响计算时search-first在发明辅助函数或重新实现仓库本地工具之前security-review当涉及认证、使用限制、授权或密钥时verification-loop用于证明重试安全性和精确的修复后状态tdd-workflow当修复需要在 worker、路由器或计费路径中添加回归测试覆盖时
使用时机
- 用户提及 ECC Tools 消耗率、PR 递归、过度创建的 PR、使用限制绕过或付费模型泄漏
- 任务位于兄弟仓库
ECC-Tools中，并依赖于 webhook 处理器、队列 worker、使用预留、PR 创建逻辑或付费网关强制执行 - 客户报告称应用创建了过多 PR、计费错误，或分析了代码但未产生可用结果
范围约束
- 在兄弟仓库
ECC-Tools中工作，而非everything-claude-code - 除非用户明确要求修复，否则以只读方式开始
- 在追踪分析消耗时，不要修改无关的计费、结账或 UI 流程
- 将应用生成的分支和应用生成的 PR 视为红旗递归路径，除非被证明并非如此
- 明确区分三件事：
- 仓库侧消耗的根本原因
- 面向客户的计费影响
- 需要纳入待办事项跟踪的产品或授权缺口
工作流
1. 冻结仓库范围
- 切换到兄弟仓库
ECC-Tools - 首先检查分支和本地差异
- 确定审计的具体范围：
- webhook 路由器
- 队列生产者
- 队列消费者
- PR 创建路径
- 使用预留 / 计费路径
- 模型路由路径
2. 在理论化之前追踪入口
- 首先检查
src/index.*或主入口点 - 在提出修复建议之前，映射每个入队路径
- 确认哪些 GitHub 事件共享一个队列类型
- 确认 push、pull_request、synchronize、comment 或手动重新运行事件是否会汇聚到同一个昂贵的路径上
3. 追踪 Worker 和副作用
- 检查处理分析的队列消费者或定时 worker
- 确认排队的分析是否总是以以下方式结束：
- PR 创建
- 分支创建
- 文件更新
- 付费模型调用
- 使用量增加
- 如果分析可能消耗令牌，然后在输出持久化之前失败，则将其归类为“消耗但输出中断”
4. 审计高信号消耗路径
PR 倍增
- 检查 PR 辅助函数和分支命名
- 检查去重、synchronize 事件处理以及现有 PR 的复用
- 如果应用生成的分支可以重新进入分析，则将其视为优先级为 0 的递归风险
配额绕过
- 检查配额检查的位置与使用量预留或增加的位置
- 如果在入队前检查配额，但仅在 worker 内部计费使用量，则将并发的前门通过视为真正的竞态条件
付费模型泄漏
- 检查模型选择、层级分支和提供商路由
- 验证当存在付费密钥时，免费或受限用户是否仍能访问付费分析器
重试消耗
- 检查重试循环、重复的队列任务和确定性失败重试
- 如果相同的非临时性错误可以反复消耗分析资源，则先修复此问题，再进行质量改进
5. 按消耗顺序修复
如果用户要求代码更改，请按以下顺序优先修复：
- 阻止自动 PR 倍增
- 阻止配额绕过
- 阻止付费模型泄漏
- 阻止重复任务扇出和无意义的重试
- 弥补重试/更新安全缺口
除非同一根本原因明显跨越多个文件，否则将修复范围限制在一到三个直接修复。
6. 以最小的验证步骤进行验证
- 仅重新运行覆盖已更改路径的目标测试或集成片段
- 验证消耗路径现在是否：
- 被阻止
- 已去重
- 降级为更便宜的分析
- 或提前被拒绝
- 准确说明最终状态：
- 本地已更改
- 本地已验证
- 已推送
- 已部署
- 仍被阻止
高信号故障模式
1. 所有触发器使用同一队列类型
如果推送、PR 同步和手动审计都入队相同的任务，并且 worker 总是创建 PR，那么分析就等于 PR 垃圾信息。
2. 入队后预留使用量
如果在入口处检查使用量，但仅在 worker 中增加，则并发请求可能全部通过关卡并超出配额。
3. 免费层级走付费路径
如果存在密钥时，免费的排队任务仍能路由到 Anthropic 或其他付费提供商，即使客户从未看到付费结果，这也是真实的支出泄漏。
4. 应用生成的分支重新进入 Webhook
如果 pull_request.synchronize、分支推送或评论触发的运行在应用拥有的分支上触发，则应用可以递归分析自己的输出。
5. 在持久化安全之前执行昂贵操作
如果系统可能消耗令牌，然后在 PR 创建、文件更新或分支冲突时失败，则是在消耗成本而不产生价值。
陷阱
- 不要一开始就广泛浏览仓库；先确定 webhook -> 队列 -> worker 的路径
- 不要将客户计费推断与基于代码的产品事实混为一谈
- 在最高消耗路径被控制之前，不要修复价值较低的质量问题
- 在重新运行狭窄的验证步骤之前，不要声称消耗问题已修复
- 除非用户要求，否则不要推送或部署
- 如果无关的仓库本地更改正在进行中，不要触碰它们
验证
- 根本原因需引用确切的文件路径和代码区域
- 修复按消耗影响排序，而非代码整洁度
- 需指明验证命令的名称
- 最终状态需区分本地更改、验证、推送和部署
- Source repo
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/ecc-tools-cost-audit/SKILL.md
- Commit SHA
- 4e973d3eaf92
- Repository license
- MIT
- Data collected