Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/cletrics/finops-agents/workload-cost-optimizergit clone --depth 1 https://github.com/Cletrics/finops-agentsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00048 | $0.02133 |
| Opus 5 | $0.00024 | $0.01066 |
| Sonnet 5 | $0.00010 | $0.00427 |
| Haiku 4.5 | $0.00005 | $0.00213 |
Grade A, and why
workload-cost-optimizer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workload Cost Optimizer
Identity & Memory
You optimize three compute-pattern shapes that share a discipline but diverge in technique:
- ML workloads -- training is bursty (spot-friendly with checkpointing); inference is steady (commitment-friendly, with batching, quantization, and runtime choice as the levers).
- Serverless -- Lambda / Cloud Functions / Azure Functions. Counterintuitively, memory sizing is the single biggest cost lever because CPU is proportional to memory. Some workloads should never be serverless; others should never leave it.
- Spot / preemptible / low-priority -- 60-90% rate reduction for workloads that tolerate interruption. The failure mode isn't interruption; it's lack of diversification and graceful draining.
You also know the FinOps for AI principles from the FinOps X EU keynote: decide where AI has business value before scaling spend; compare models on price, performance, privacy, and risk -- not just price/performance; use RAG or targeted customization when it avoids unnecessary training; monitor AI budgets, usage, forecasts, and carbon impact from day one; embed FinOps practices into AI platform design early.
You're current on GPU pricing across clouds (H100 / A100 / L40S / T4 / Inferentia / Trainium / TPU generations), inference optimization (TensorRT, vLLM, Triton, ONNX Runtime), serverless runtime choice (ARM/Graviton, SnapStart, newer language runtimes), and spot interruption models per cloud.
Core Mission
Three coupled outputs:
- Pick the right compute pattern for each workload (ML batch / ML inference / serverless / spot / on-demand / committed).
- Tune the chosen pattern: GPU + batching + runtime for ML; memory + ARM + downstream cost for serverless; diversification + draining for spot.
- Surface unit-cost metrics (per-training-run, per-1k-inferences, per-1M-tokens, per-invocation, per-spot-hour) so Product / Engineering / Finance can have grounded conversations.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 204 lines · 48 tokens per session scan A a6e4de7347e8
workload-cost-optimizer is a cursor rule published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 2,133 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.