by globalmpc
Claude Code skill that estimates what your vibe-coded app will cost to run at 100 / 1k / 10k / 100k users, flags code patterns that inflate the bill, and renders a shareable receipt.
# Add to your Claude Code skills
git clone https://github.com/globalmpc/vibe-billGuides for using cli tools skills like vibe-bill.
See how vibe-bill compares with popular alternatives.
vibe-bill is an open-source cli tools skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by globalmpc. Claude Code skill that estimates what your vibe-coded app will cost to run at 100 / 1k / 10k / 100k users, flags code patterns that inflate the bill, and renders a shareable receipt. It has 50 GitHub stars.
vibe-bill's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/globalmpc/vibe-bill" and add it to your Claude Code skills directory (see the Installation section above).
vibe-bill is primarily written in TypeScript. It is open-source under globalmpc on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other CLI Tools skills you can browse and compare side by side. Open the CLI Tools category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh vibe-bill against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.

Example receipt generated from a fixture app in this repo (fixtures/next-openai-supabase), not a real project.
You built an app with AI. What will it cost to run when people actually use it?
vibe-bill is a Claude Code skill. Type /vibe-bill in your project and it:
You need Claude Code and Node 22 or newer (check with node -v).
Easiest: run this in your project's folder.
npx skills add globalmpc/vibe-bill -a claude-code
No npx? Copy it by hand instead (Node 20 is enough to run the skill itself):
git clone https://github.com/globalmpc/vibe-bill.git /tmp/vibe-bill
mkdir -p .claude/skills && cp -r /tmp/vibe-bill/skills/vibe-bill .claude/skills/
Or just ask Claude Code: "Install the vibe-bill skill from https://github.com/globalmpc/vibe-bill into this project."
/vibe-bill..vibe-bill/out/receipt.png. That's your receipt. .vibe-bill/out/report.md explains the numbers.Want no questions at all? Type /vibe-bill --no-questions.
Share the receipt, not the report. The receipt never shows file names, secret names or secrets. The report does mention file names from your code.
OPENAI_API_KEY), never what's inside them. It will not open your .env files..vibe-bill/ folder in your project.(unverified).By default, vibe-bill uses a saved price list, so running it twice gives the same numbers. The date is printed on the receipt.
/vibe-bill . use fresh prices (the . means "this folder").vibe-bill finds your AI provider from your code: the SDK package or an env name like ANTHROPIC_API_KEY. If your app talks to Claude through a proxy, none of that is there, so it can't see the provider.
When it finds AI calls but no provider, it asks you which one (OpenAI, Anthropic, Google AI or OpenRouter) and remembers the answer. With --no-questions it stops and tells you what to add. You can also set it yourself in .vibe-bill/config.json:
{ "schema": 1, "llm_providers": ["anthropic"] }
Then run /vibe-bill again. The model question that follows ("Which model does production use?") is where you pick Sonnet, Haiku and so on.
The receipt shows 10,000 users. The report has a column for each of 100, 1,000, 10,000 and 100,000. Want to see 1,000,000 (or any other number)?
.vibe-bill/config.json and run /vibe-bill again:{ "schema": 1, "assumptions": { "tiers": [1000, 100000, 1000000] } }
You can list 1 to 6 whole numbers. The receipt shows the 10,000 one if it's in your list; otherwise it shows the biggest. With "tiers": [1000000] you get a receipt and a report just for 1M users.
Every guess (active users per day, messages per user per day, ...) is listed in the report with the reason for it. To change one, put your own number in .vibe-bill/config.json and run /vibe-bill again:
{ "schema": 1, "assumptions": { "messages_per_active_user_per_day": 12 } }
The full list of guesses is in data/assumptions.default.json. If editing JSON feels like too much, ask Claude Code: "Set messages per user per day to 12 for vibe-bill and rerun it."
Price corrections are the most useful help. See CONTRIBUTING.md.
MIT, see LICENSE. Third-party parts bundled in skills/vibe-bill/scripts/ keep their own licenses and are listed in THIRD_PARTY_NOTICES.md.