caveman-setup

Wire repository LLM callsites through the Caveman gateway for cost and latency measurement.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/bittlinkm/claude-setup --skill caveman-setup-bittlinkm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-setup
Source: https://github.com/bittlinkm/claude-setup/tree/main/skills/caveman-setup
Command: npx skills add https://github.com/bittlinkm/claude-setup --skill caveman-setup-bittlinkm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Applications calling LLM providers have no visibility into what each request costs, how many tokens it uses, or how long it takes. This Skill integrates the Caveman gateway into an existing repository so every LLM request is measured without changing application behavior. ## Core Features & Use Cases - Callsite Discovery: Scans dependency files and source code for OpenAI, Anthropic, Vercel AI SDK, LangChain, LiteLLM, and raw HTTP LLM callsites before making any changes. - Gateway Wiring: Rewrites each callsite's base URL to the gateway path with an app slug and adds the x-cave-api-key auth header, supporting both stored and byok provider-key modes. - Verified Integration: Sends one real verification request through the new wiring and reports the actual HTTP status and token usage, with verbatim failure templates for unreachable gateways, invalid keys, and routing errors. - Use Case: A developer pastes the Caveman setup prompt into their support-bot repo; the Skill finds the OpenAI SDK client, points it at the gateway, verifies with a real request, and the spend appears on the dashboard grouped under the app slug. ## Quick Start Paste the Caveman setup prompt containing the gateway URL and Cave API key, or say "set up caveman" to wire this repository's LLM calls through the gateway.

Frequently Asked Questions about caveman-setup

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

FAQPage Schema
How do I add LLM cost tracking to my application?

Point each LLM client's base URL at the Caveman gateway path with your app slug and add the x-cave-api-key header. The gateway measures cost, tokens, and latency per request without changing model behavior, and results appear on the dashboard.

Which LLM SDKs work with the Caveman gateway?

Published recipes cover OpenAI SDK (TypeScript and Python), Anthropic SDK, Vercel AI SDK, LangChain and LangGraph, LiteLLM, and raw HTTP calls. Frameworks like google-genai, crewai, and pydantic-ai have integration pages under the docs origin.

Does the gateway change my model requests or responses?

No. In record mode the gateway is byte-preserving: it measures what your app sends and what it costs and changes nothing else. No optimization is enabled and verified savings remain $0 until an optimizer is explicitly turned on.

Where does my provider API key go when using the gateway?

In stored mode, provider keys live encrypted in Caveman Cloud and you never handle one. In byok mode, your existing provider key stays where it already is and is sent per request via the x-cave-upstream-key header.

Why does gateway verification return 401 or 404?

A 401 cave_invalid_api_key means the gateway rejected the Cave API key; mint a new one from the dashboard and update the env file. A 404 cave_route_not_found usually means a malformed app slug or a path that does not match the SDK's protocol.