llm-cost-rate-governance

Validates Anthropic SDK call sites for rate-limit handling, retries, and graceful degradation.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/elchananteitzwork-a11y/supplement-intelligence --skill llm-cost-rate-governance-elchananteitzwork-a11y
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: llm-cost-rate-governance
Source: https://github.com/elchananteitzwork-a11y/supplement-intelligence/tree/main/.claude/skills/llm-cost-rate-governance
Command: npx skills add https://github.com/elchananteitzwork-a11y/supplement-intelligence --skill llm-cost-rate-governance-elchananteitzwork-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production pipelines that call the Anthropic API can crash or block all analyses when credits are exhausted, rate limits hit, or errors go unhandled. This Skill enforces a governance checklist so every Claude call site handles 429s, retries transient failures, and degrades gracefully instead of surfacing raw provider errors. ## Core Features & Use Cases - Rate-Limit and Credit-Exhaustion Checks: Confirms every Anthropic SDK call catches 429 and insufficient-credit responses explicitly. - Bounded Retry and Degradation Rules: Requires backoff-based retries and a LIMITED-confidence fallback result on exhaustion. - Cost Traceability: Ensures new call sites document model and approximate token volume for later cost review. - Use Case: When adding a new pipeline stage in lib/stage2 that calls anthropic.messages.create(), apply this Skill to verify error handling, retry bounds, and context truncation before shipping. ## Quick Start Review the new Claude API call I just added in lib/thesis-engine and check it against the LLM cost and rate governance checklist.

Frequently Asked Questions about llm-cost-rate-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle Anthropic API rate limits in a pipeline?▼

Catch 429 and insufficient-credit responses explicitly around each anthropic.messages.create() call, retry transient failures with bounded backoff, and on exhaustion return a LIMITED-confidence result with a clear message instead of propagating the raw error.

What should a Claude call site do when API credits are exhausted?▼

It must not crash the pipeline or surface an unhandled exception. After bounded retries are exhausted, it should degrade gracefully by returning a LIMITED-tier result stating the analysis was not possible with available data.

Does this governance apply to non-Anthropic LLM providers?▼

No. This Skill covers Anthropic SDK call sites only. Non-LLM or other provider integrations fall under the separate data-provider-integration-contract scope, and UI edits or mocked tests are also out of scope.

When should I apply LLM cost governance checks?▼

Apply them whenever creating or editing a file that imports @anthropic-ai/sdk or adding a new pipeline stage that consumes Claude. Do not apply them to tests that only mock the Anthropic client.

Why must prompt context be bounded before calling Claude?▼

Unbounded prompt growth drives excessive token usage and cost. Inputs should be truncated or summarized before reaching the model, with documentation of why the chosen context size is sufficient.