We’re launching llm-waste-audit with a minimal but honest MVP focused on two common and expensive waste patterns:
- W1 — Context Bloat
- W2 — Cache Breaker
The broader taxonomy is already documented:
- W1 — Context Bloat
- W2 — Cache Breaker
- W3 — Redundant Reasoning
- W4 — Model Overkill
- W5 — Output Excess
- W6 — Retrieval Waste
- W7 — Session Memory Failure
- W8 — Unsafe Semantic Reuse
We want help expanding it with real production patterns.
If you’ve seen a recurring, avoidable LLM waste pattern, please comment or open a new issue with:
- A short name or description of the pattern
- Why it increases cost, latency, or token usage
- A minimal reproducible example (JSON preferred)
- Whether it is provider-specific or general
- The rough savings you would expect if fixed
We strongly prefer concrete examples over abstract opinions.
This repo is meant to be a living technical benchmark, not a marketing artifact.
We’re launching
llm-waste-auditwith a minimal but honest MVP focused on two common and expensive waste patterns:The broader taxonomy is already documented:
We want help expanding it with real production patterns.
If you’ve seen a recurring, avoidable LLM waste pattern, please comment or open a new issue with:
We strongly prefer concrete examples over abstract opinions.
This repo is meant to be a living technical benchmark, not a marketing artifact.