LLM Cost Optimizer

SkillAI & models

Know what your AI is costing you and get practical ways to spend less. Once added, your AI can analyze your API costs and suggest savings, like sending routine tasks to cheaper models. It also steps in whenever cost questions come up, from choosing a model to lowering token usage.

Available today. Use it from your connected AI after setup.

After adding it, just bring up your AI costs in a normal conversation, for example ask it to review your API spending or recommend a cheaper model. It also jumps in on its own whenever cost topics come up.

Then ask your AI: use the LLM Cost Optimizer skill

What your AI can do with it

  • Analyze your AI API costs
  • Suggest ways to cut spending, like routing tasks to cheaper models
  • Help you pick the right model for each task
  • Find opportunities to reduce token usage
  • Guide you through implementing prompt caching
  • Advise on costs when you are planning an AI feature or building an AI endpoint

What this skill tells your AI

The instructions your AI receives, as published by borghei/claude-skills in engineering/llm-cost-optimizer/SKILL.md and read by ahel’s review.

Category: Engineering Domain: AI Cost Management

Overview

The LLM Cost Optimizer skill provides tools for counting tokens, estimating costs across different LLM providers, and optimizing prompts to reduce token usage without sacrificing quality. Essential for teams managing LLM API budgets at scale.

Clarify First

Before estimating or optimizing, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Input prompt/text — the prompt file or text to count or optimize (the input via --file/--text/--stdin)
  • Target models — which models to estimate cost for (sets --models and the pricing comparison)
  • Goal — cost estimation vs prompt optimization, and any target reduction (selects token_counter.py vs prompt_optimizer.py and sets --target-reduction)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

# Count tokens in a prompt file and estimate costs
python scripts/token_counter.py --file prompt.txt --models gpt-4o claude-sonnet

# Count tokens from stdin
echo "Hello world" | python scripts/token_counter.py --stdin --models all

# Analyze a prompt for optimization opportunities
python scripts/prompt_optimizer.py --file system_prompt.txt

# Optimize with target reduction
python scripts/prompt_optimizer.py --file prompt.txt --target-reduction 30

Tools Overview

ToolPurposeKey Flags
token_counter.pyCount tokens and estimate costs across models--file, --text, --stdin, --models
prompt_optimizer.pyAnalyze prompts for token reduction opportunities--file, --target-reduction, --format
cache_savings_calculator.pyModel prompt-cache economics: naive vs cached cost, break-even reuse, % savings--requests, --cached-tokens, --cache-write-multiplier, --cache-read-multiplier, --base-input-price, --json

Workflows

Cost Estimation for New Project

  1. Collect sample prompts (system prompt + user messages)
  2. Run token_counter.py with target models
  3. Multiply per-request cost by expected daily volume
  4. Compare models on cost-quality tradeoff

Prompt Optimization Sprint

  1. Identify highest-cost prompts from usage logs
  2. Run prompt_optimizer.py on each
  3. Apply suggested optimizations
  4. Re-count tokens to verify reduction
  5. A/B test optimized vs. original for quality

Reference Documentation

  • LLM Pricing Guide - Current pricing for major LLM providers, token estimation methods
  • Caching & Batch Economics - Prompt/context caching break-even math, batch-API cost tradeoff, reasoning-effort cost impact, structured-output token overhead (model-agnostic, user-supplied rates)

Common Patterns

Token Reduction Techniques

  • Remove redundant instructions and examples
  • Use shorter variable names in few-shot examples
  • Compress verbose system prompts
  • Replace repeated context with references
  • Use structured output formats (JSON) to reduce response tokens
  • Batch multiple requests into single prompts where possible

Cost-Effective Model Selection

  • Use smaller models for classification/extraction tasks
  • Reserve large models for complex reasoning
  • Implement model routing based on query complexity
  • Cache responses for identical or similar queries
  • Cache the stable system-prompt/context/schema prefix (most-stable first, volatile last) and check the reuse break-even with cache_savings_calculator.py
  • Route bulk, non-interactive work to the batch API (~half cost for added latency); right-size reasoning effort per route — high only where accuracy demands it

Signals

GitHub stars
752
Forks
137
Last commit
Aug 2026

ahel review

  • K6low
    bundled executables the agent is told to run

Automated review, not a security audit. Ruleset v1+k2.

Advanced
Catalog kind
skill
Gateway key
llm-cost-optimizer
Source
github.com/borghei/claude-skills