Individual skill

llm-cost-latency-budget

Model the cost and latency of an LLM feature before it ships and surprises the bill. Use when asked to estimate LLM API costs, set a latency/token budget, decide which model tier to use, or bring down the cost of an AI feature. Produces a cost & latency budget — token math per request, monthly cost projection, model tiering, caching/streaming levers, p95 latency targets, and a guardrail/alert plan.

plugins/pm-ai/skills/llm-cost-latency-budget/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# LLM Cost & Latency Budget Skill

LLM features have a unit cost and a tail latency that demos hide and production exposes. This skill does
the token math up front — what one request costs, what a million cost, where the p95 latency comes from —
and lays out the levers (model tiering, caching, prompt trimming) so cost and speed are designed, not discovered.

## Required Inputs

Ask for these only if they aren't already provided:

- **The request shape** — typical system prompt, user input, retrieved context, and output sizes (in rough tokens).
- **Volume** — requests/day now and at target scale; peak concurrency.
- **Models in play** — candidate model(s) and their per-token input/output prices.
- **Targets** — acceptable cost per request (or per user/month) and the latency users will tolerate (p50 / p95).
Back to top