vibe-billing-scan
Find which OpenClaw run, session, or retry storm is costing you money. One command. No signup. Runs locally.
When to Use
Activate this skill when the user:
- - Says their API bill is higher than expected
- Wants to know which run or session cost the most
- Suspects a retry loop or rate-limit storm
- Asks about token usage, spending, or waste
- Uses phrases like: "why is my bill high", "find the bad run", "scan my spend", "check api costs", "retry loop", "bill shock"
What This Does
Runs npx vibe-billing scan against the user's local OpenClaw logs and API proxy data. Returns:
- 1. Which session/run cost the most — ranked by spend
- Retry storm detection — flags runs where 429 errors caused expensive retry chains
- Context accumulation analysis — shows sessions where the context window grew unusually large
- Looped tool call detection — identifies tool calls that repeated more than expected
- Total spend summary — across all tracked requests
Quick Reference
CODEBLOCK0
Step-by-Step Instructions
Step 1 — Run the scan
Tell the user to run this in their terminal:
CODEBLOCK1
Step 2 — Interpret the output
- - Requests: total API calls tracked
- Money Saved: estimated waste intercepted
- Tokens Saved: tokens deduplicated or cached
- Loops Blocked: retry storms stopped
Step 3 — Identify the bad run
Almost always caused by one of:
- 1. Retry storm — agent hit 429, retried multiple times, each retry re-sent full context
- Long session — 30+ turn conversation where every message re-sent all prior context
- Looped tool call — agent called the same tool repeatedly on unexpected output
Step 4 — Set up ongoing monitoring (optional)
CODEBLOCK2
Proof
- - $7,691 saved across tracked requests
- 947 million tokens intercepted
- 161 loops blocked
Landing Page
https://api.jockeyvc.com
vibe-billing-scan
找出哪个OpenClaw运行、会话或重试风暴正在消耗你的资金。一条命令。无需注册。本地运行。
使用时机
当用户出现以下情况时激活此技能：
- - 表示API账单高于预期
- 想知道哪个运行或会话成本最高
- 怀疑存在重试循环或速率限制风暴
- 询问关于令牌使用、支出或浪费的问题
- 使用类似这样的表述：为什么我的账单这么高、找出问题运行、扫描我的支出、检查API成本、重试循环、账单冲击
功能说明
针对用户本地的OpenClaw日志和API代理数据运行npx vibe-billing scan命令。返回结果：
- 1. 成本最高的会话/运行 — 按支出排序
- 重试风暴检测 — 标记因429错误导致昂贵重试链的运行
- 上下文累积分析 — 显示上下文窗口异常增大的会话
- 循环工具调用检测 — 识别重复次数超出预期的工具调用
- 总支出汇总 — 涵盖所有追踪的请求
快速参考
npx vibe-billing scan # 扫描现有日志，无需配置
npx vibe-billing setup # 为未来运行安装代理（可选）
npx vibe-billing status # 显示实时运行状态
分步说明
第一步 — 运行扫描
告诉用户在终端中运行以下命令：
bash
npx vibe-billing scan
第二步 — 解读输出结果
- - 请求数：追踪的API调用总数
- 节省金额：拦截的预估浪费支出
- 节省令牌：去重或缓存的令牌数
- 阻止循环：阻止的重试风暴次数
第三步 — 识别问题运行
几乎总是由以下原因之一导致：
- 1. 重试风暴 — 代理遇到429错误，多次重试，每次重试都重新发送完整上下文
- 长会话 — 超过30轮的对话，每条消息都重新发送之前的所有上下文
- 循环工具调用 — 代理对意外输出重复调用同一工具
第四步 — 设置持续监控（可选）
bash
npx vibe-billing setup
数据证明
- - 在追踪请求中节省了7,691美元
- 拦截了9.47亿个令牌
- 阻止了161个循环
落地页
https://api.jockeyvc.com
