返回顶部
v

vibe-billing-scan

Scan your OpenClaw API spend and find which run, session, or retry storm is costing you money. Use when your API bill looks too high, when you want to see per-session costs, or when you suspect a retry loop. Triggers: "why is my bill high", "scan my api spend", "check my costs", "vibe billing", "find expensive run", "retry loop cost", "api bill too high".

作者: admin | 来源: ClawHub
源自
ClawHub
版本
V 1.0.0
安全检测
已通过
87
下载量
0
收藏
概述
安装方式
版本历史

vibe-billing-scan

# 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 2. **Retry storm detection** — flags runs where 429 errors caused expensive retry chains 3. **Context accumulation analysis** — shows sessions where the context window grew unusually large 4. **Looped tool call detection** — identifies tool calls that repeated more than expected 5. **Total spend summary** — across all tracked requests ## Quick Reference ``` npx vibe-billing scan # scan existing logs, no setup needed npx vibe-billing setup # install proxy for future runs (optional) npx vibe-billing status # show live runtime stats ``` ## Step-by-Step Instructions ### Step 1 — Run the scan Tell the user to run this in their terminal: ```bash npx vibe-billing scan ``` ### 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 2. Long session — 30+ turn conversation where every message re-sent all prior context 3. Looped tool call — agent called the same tool repeatedly on unexpected output ### Step 4 — Set up ongoing monitoring (optional) ```bash npx vibe-billing setup ``` ## Proof - $7,691 saved across tracked requests - 947 million tokens intercepted - 161 loops blocked ## Landing Page https://api.jockeyvc.com

标签

skill ai

通过对话安装

该技能支持在以下平台通过对话安装:

OpenClaw WorkBuddy QClaw Kimi Claude

方式一:安装 SkillHub 和技能

帮我安装 SkillHub 和 vibe-billing-scan-1776018601 技能

方式二:设置 SkillHub 为优先技能安装源

设置 SkillHub 为我的优先技能安装源,然后帮我安装 vibe-billing-scan-1776018601 技能

通过命令行安装

skillhub install vibe-billing-scan-1776018601

下载 Zip 包

⬇ 下载 vibe-billing-scan v1.0.0

文件大小: 2.47 KB | 发布时间: 2026-4-13 12:27

v1.0.0 最新 2026-4-13 12:27
Initial release of vibe-billing-scan.

- Scans OpenClaw API usage to identify high-cost runs, sessions, or retry storms.
- Detects expensive retry loops, large context windows, and repeated tool calls.
- Provides a spend summary and detailed breakdown of where your API bill is going.
- Requires no signup; runs locally with one terminal command.
- Includes optional setup for ongoing monitoring.

Archiver·手机版·闲社网·闲社论坛·羊毛社区· 多链控股集团有限公司 · 苏ICP备2025199260号-1

Powered by Discuz! X5.0   © 2024-2025 闲社网·线报更新论坛·羊毛分享社区·http://xianshe.com

p2p_official_large
返回顶部