← ClaudeAtlas

cost-policelisted

Find where a codebase wastes money on LLM tokens, metered services, and cloud infrastructure, show the dollar math for every finding with live prices cited from official pages, flag where one bug or one abuser could run up the bill, and refuse savings claims that cannot be verified. Use for requests about a bill that is too high or doubled, API costs, token spend, a surprise or runaway bill, a Firebase, Firestore, AWS, GCP, Azure, Vercel, Supabase, Twilio, OpenAI, Anthropic, or Gemini bill, cost per user or per request, whether a free tier is affordable, whether this could bankrupt me at launch, denial of wallet, Terraform, CloudFormation, CDK, Pulumi, or serverless cost, infra cost, or cutting cloud spend. Also triggers on speech-to-text forms like cost police, coast police, cost-pleas, or cost please. Time and memory complexity questions go to big-o-police. Report only by default; change code or infrastructure only when the user explicitly asks for fixes.
varuntej07/tej-stack · ★ 1 · DevOps & Infrastructure · score 74
Install: claude install-skill varuntej07/tej-stack
# Cost Police > **Update check (run silently before the audit):** run `bash "<this skill's directory>/../../bin/check-update.sh"` and read its single `TEJ_STACK:` status line. If it reports `UPGRADE_AVAILABLE`, tell the user once, in one line, that a newer Tej Stack is available and they can upgrade with `/plugin update tej-stack@tej-stack` (changes listed in the repo's CHANGELOG.md), then continue this task normally. On `UP_TO_DATE` or `CHECK_SKIPPED`, or if the script is missing or errors, say nothing and continue. The check must never block, delay, or fail the task. Find where the money goes, where one mistake could make it go much faster, and what each fix is worth in dollars, with the arithmetic shown. The mandate is not to make the bill smaller at any price. It is to name the call site, price it from a live official source, show the math, and say plainly when a saving cannot be proven. Default to a report. Do not edit code, prompts, or infrastructure unless the user explicitly asks for fixes. **The failure this skill exists to prevent is not a high bill. It is a confident dollar figure nobody can check.** A made-up saving reads exactly like a real one. Every number must carry its prices, its volume, and a way to be proven wrong. ## 1. Three lenses | Lens | The question | Catalog | |---|---|---| | **Token and API waste** | Where does steady spend leak on LLM and metered API calls? | [references/waste-catalog.md](references/waste-catalog.md) | | **Runaway risk** |