PluginBench
Skill
Pass
Audit score 90

cost-aware-llm-pipeline

affaan-m/ecc

Route models by task complexity, track costs immutably, retry safely, and cache prompts to optimize LLM API spend.

What is cost-aware-llm-pipeline?

Cost optimization patterns for LLM API applications combining model routing by complexity, immutable budget tracking, transient-only retry logic, and prompt caching. Use this when building production LLM pipelines that need to stay within budget while maintaining quality on complex tasks.

  • Route between cheaper (Haiku) and expensive (Sonnet/Opus) models based on text length and item count thresholds
  • Track cumulative API costs with immutable dataclasses to prevent state mutation bugs
  • Retry only on transient errors (connection, rate limit, server error) and fail fast on permanent failures (auth, bad request)
  • Cache long system prompts using ephemeral cache control to reduce token spend and latency
  • Compose all four techniques into a single pipeline function with budget guardrails

How to install cost-aware-llm-pipeline

npx skills add null --skill cost-aware-llm-pipeline
Prerequisites
  • Python 3.10+
  • Anthropic SDK (or similar LLM client library)
  • Access to Claude API with billing configured
Claude Code
Cursor
Windsurf
Cline

How to use cost-aware-llm-pipeline

  1. 1.Define model selection thresholds based on your task complexity (text length, item count)
  2. 2.Create a CostTracker instance with your budget limit in USD
  3. 3.Implement select_model() to route between Haiku and Sonnet based on input size
  4. 4.Wrap API calls with call_with_retry() to handle only transient errors
  5. 5.Add prompt caching headers to system prompts over 1024 tokens
  6. 6.Compose all four into a process() function that checks budget, routes model, calls with retry, and tracks cost immutably
  7. 7.Log model selection decisions to tune thresholds based on real usage patterns

Use cases

Good for
  • Batch processing documents of varying complexity where simple items use Haiku and complex analysis uses Sonnet
  • Building a chatbot that must stay within a monthly API budget by routing simple queries to cheaper models
  • Processing customer support tickets where triage uses Haiku and escalated cases use Opus
  • Implementing a multi-tenant SaaS where each customer has a cost limit enforced before API calls
  • Optimizing a content generation pipeline that caches the same system prompt across thousands of requests
Who it's for
  • Backend engineers building production LLM applications
  • Data engineers processing large batches with LLM APIs
  • Product teams managing API costs in multi-model architectures
  • Developers optimizing cost without sacrificing quality on complex tasks

cost-aware-llm-pipeline FAQ

When should I use Haiku vs Sonnet?

Use Haiku (3-4x cheaper) for simple tasks: short text, basic classification, simple extraction. Route to Sonnet for complex reasoning, long documents (>10k chars), or batches >30 items. Adjust thresholds based on your accuracy requirements.

How much does prompt caching save?

Caching saves 90% on cached tokens after the first request. For a 2000-token system prompt, the first call pays full price; subsequent calls pay 10% of input token cost for those tokens.

What errors should I retry on?

Only retry on transient errors: APIConnectionError, RateLimitError, InternalServerError. Fail immediately on AuthenticationError and BadRequestError—retrying won't help and wastes budget.

Can I use this with OpenAI or other providers?

Yes. The patterns (routing, tracking, retry, caching) are provider-agnostic. Adjust model names, pricing, and error types to match your provider's API.

How do I tune complexity thresholds?

Start conservative (route to expensive model early). Log every model selection decision with input metrics. After 100+ calls, analyze which decisions were correct vs incorrect and adjust thresholds upward if the cheaper model performed well.

Full instructions (SKILL.md)

Source of truth, from affaan-m/ecc.


name: cost-aware-llm-pipeline description: Cost optimization patterns for LLM API usage — model routing by task complexity, budget tracking, retry logic, and prompt caching. metadata: origin: ECC

Cost-Aware LLM Pipeline

Patterns for controlling LLM API costs while maintaining quality. Combines model routing, budget tracking, retry logic, and prompt caching into a composable pipeline.

When to Activate

  • Building applications that call LLM APIs (Claude, GPT, etc.)
  • Processing batches of items with varying complexity
  • Need to stay within a budget for API spend
  • Optimizing cost without sacrificing quality on complex tasks

Core Concepts

1. Model Routing by Task Complexity

Automatically select cheaper models for simple tasks, reserving expensive models for complex ones.

MODEL_SONNET = "claude-sonnet-4-6"
MODEL_HAIKU = "claude-haiku-4-5-20251001"

_SONNET_TEXT_THRESHOLD = 10_000  # chars
_SONNET_ITEM_THRESHOLD = 30     # items

def select_model(
    text_length: int,
    item_count: int,
    force_model: str | None = None,
) -> str:
    """Select model based on task complexity."""
    if force_model is not None:
        return force_model
    if text_length >= _SONNET_TEXT_THRESHOLD or item_count >= _SONNET_ITEM_THRESHOLD:
        return MODEL_SONNET  # Complex task
    return MODEL_HAIKU  # Simple task (3-4x cheaper)

2. Immutable Cost Tracking

Track cumulative spend with frozen dataclasses. Each API call returns a new tracker — never mutates state.

from dataclasses import dataclass

@dataclass(frozen=True, slots=True)
class CostRecord:
    model: str
    input_tokens: int
    output_tokens: int
    cost_usd: float

@dataclass(frozen=True, slots=True)
class CostTracker:
    budget_limit: float = 1.00
    records: tuple[CostRecord, ...] = ()

    def add(self, record: CostRecord) -> "CostTracker":
        """Return new tracker with added record (never mutates self)."""
        return CostTracker(
            budget_limit=self.budget_limit,
            records=(*self.records, record),
        )

    @property
    def total_cost(self) -> float:
        return sum(r.cost_usd for r in self.records)

    @property
    def over_budget(self) -> bool:
        return self.total_cost > self.budget_limit

3. Narrow Retry Logic

Retry only on transient errors. Fail fast on authentication or bad request errors.

from anthropic import (
    APIConnectionError,
    InternalServerError,
    RateLimitError,
)

_RETRYABLE_ERRORS = (APIConnectionError, RateLimitError, InternalServerError)
_MAX_RETRIES = 3

def call_with_retry(func, *, max_retries: int = _MAX_RETRIES):
    """Retry only on transient errors, fail fast on others."""
    for attempt in range(max_retries):
        try:
            return func()
        except _RETRYABLE_ERRORS:
            if attempt == max_retries - 1:
                raise
            time.sleep(2 ** attempt)  # Exponential backoff
    # AuthenticationError, BadRequestError etc. → raise immediately

4. Prompt Caching

Cache long system prompts to avoid resending them on every request.

messages = [
    {
        "role": "user",
        "content": [
            {
                "type": "text",
                "text": system_prompt,
                "cache_control": {"type": "ephemeral"},  # Cache this
            },
            {
                "type": "text",
                "text": user_input,  # Variable part
            },
        ],
    }
]

Composition

Combine all four techniques in a single pipeline function:

def process(text: str, config: Config, tracker: CostTracker) -> tuple[Result, CostTracker]:
    # 1. Route model
    model = select_model(len(text), estimated_items, config.force_model)

    # 2. Check budget
    if tracker.over_budget:
        raise BudgetExceededError(tracker.total_cost, tracker.budget_limit)

    # 3. Call with retry + caching
    response = call_with_retry(lambda: client.messages.create(
        model=model,
        messages=build_cached_messages(system_prompt, text),
    ))

    # 4. Track cost (immutable)
    record = CostRecord(model=model, input_tokens=..., output_tokens=..., cost_usd=...)
    tracker = tracker.add(record)

    return parse_result(response), tracker

Pricing Reference (2025-2026)

ModelInput ($/1M tokens)Output ($/1M tokens)Relative Cost
Haiku 4.5$0.80$4.001x
Sonnet 4.6$3.00$15.00~4x
Opus 4.5$15.00$75.00~19x

Best Practices

  • Start with the cheapest model and only route to expensive models when complexity thresholds are met
  • Set explicit budget limits before processing batches — fail early rather than overspend
  • Log model selection decisions so you can tune thresholds based on real data
  • Use prompt caching for system prompts over 1024 tokens — saves both cost and latency
  • Never retry on authentication or validation errors — only transient failures (network, rate limit, server error)

Anti-Patterns to Avoid

  • Using the most expensive model for all requests regardless of complexity
  • Retrying on all errors (wastes budget on permanent failures)
  • Mutating cost tracking state (makes debugging and auditing difficult)
  • Hardcoding model names throughout the codebase (use constants or config)
  • Ignoring prompt caching for repetitive system prompts

When to Use

  • Any application calling Claude, OpenAI, or similar LLM APIs
  • Batch processing pipelines where cost adds up quickly
  • Multi-model architectures that need intelligent routing
  • Production systems that need budget guardrails