LLM Cost Optimizer
Use proactively whenever LLM API costs come up -- or should. Triggers include: 'my AI costs are too high', 'optimize token usage', 'which model should I use', 'LLM spend is out of control', 'implement prompt caching', 'we're about to launch an AI feature', 'build me an AI endpoint'. Don't wait for an explicit cost complaint -- if someone is building an AI feature, designing an LLM endpoint, or choosing between models, cost architecture belongs in the conversation. Apply immediately when any of these are true: a system prompt appears that exceeds a few hundred tokens, all requests are hitting the same model, maxtokens is not set, or no per-feature cost logging exists. NOT for RAG pipeline design (use rag-architect). NOT for improving prompt quality or effectiveness (use senior-prompt-engineer).
Works with: Claude Code, Cursor, Codex CLI
Category: Productivity — see all ranked ›
Work: Prompt engineering · Agent configuration
Who it is for: AI engineer · Agent operator
- Adoption: 1 repos
- Health: active
- GitHub stars: 23,181
- Contributors: 30
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
source ↗ · skill:alirezarezvani/llm-cost-optimizer
Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›