Show HN: CostClaw, a local CLI that finds your Claude Code spend leaks

On Hacker News under Show HN, CostClaw is listed as a local CLI that finds Claude Code spend leaks. The listing points to a single entry command, npx costclaw audit, and sits at 1 point with 0 comments on the thread at news.ycombinator.com/item?id=49179107.

As presented, CostClaw is a local CLI rather than a hosted dashboard. The surface API is the audit subcommand invoked through npx, so a developer can run the check from a terminal without installing a separate global package first. The stated job of that audit is to surface spend leaks tied to Claude Code usage.

That matters for engineers and builders who run Claude Code in day-to-day work and only see cost after the bill arrives. A local audit step gives a way to inspect where spend is leaking before the next invoice cycle, without sending project data to a third-party cost service just to get a report.

The Show HN post sits in the same HN feed slice as Claude, Codex, and Fable tooling discussions. Against that backdrop, CostClaw is not another coding agent; it is a cost-visibility tool aimed at Claude Code specifically, competing for attention with agent demos by attacking the billing side of the same workflow.

What to try next is straightforward: run npx costclaw audit against a real Claude Code usage path and judge whether the leak findings match how you actually spend. With the thread still at 1 point and no comments, early adopters should treat the HN page as the place to watch for author clarifications on scope, what “spend leak” means in practice, and how the tool decides what to flag.