Caveman Gateway Setup
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
Analyze the most expensive users in AI observability and explain why they cost so much.
Install Analyzing Expensive Users
$ npx skills add PostHog/posthog --skill analyzing-expensive-users -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog analyzing-expensive-users --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/ai_observability/skills/analyzing-expensive-users .claude/skills/analyzing-expensive-users && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analyzing-expensive-users" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/analyzing-expensive-users into .claude/skills/analyzing-expensive-users/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-expensive-users", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/analyzing-expensive-usersType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill analyzing-expensive-users -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog analyzing-expensive-users --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/ai_observability/skills/analyzing-expensive-users .agents/skills/analyzing-expensive-users && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyzing-expensive-users" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/analyzing-expensive-users into .agents/skills/analyzing-expensive-users/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-expensive-users", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill analyzing-expensive-users -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog analyzing-expensive-users --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/ai_observability/skills/analyzing-expensive-users .cursor/skills/analyzing-expensive-users && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analyzing-expensive-users" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/analyzing-expensive-users into .cursor/skills/analyzing-expensive-users/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-expensive-users", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path products/ai_observability/skills/analyzing-expensive-users--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill analyzing-expensive-users -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog analyzing-expensive-users --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/ai_observability/skills/analyzing-expensive-users .gemini/skills/analyzing-expensive-users && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analyzing-expensive-users" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/analyzing-expensive-users into .gemini/skills/analyzing-expensive-users/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-expensive-users", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog analyzing-expensive-usersInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill analyzing-expensive-users -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/ai_observability/skills/analyzing-expensive-users .github/skills/analyzing-expensive-users && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analyzing-expensive-users" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/analyzing-expensive-users into .github/skills/analyzing-expensive-users/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-expensive-users", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill analyzing-expensive-users -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog analyzing-expensive-users --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/ai_observability/skills/analyzing-expensive-users .opencode/skills/analyzing-expensive-users && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analyzing-expensive-users" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/analyzing-expensive-users into .opencode/skills/analyzing-expensive-users/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-expensive-users", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analyzing-expensive-users- GitHub stars
- 40k
- Token cost
- ~3.9k tokens
- SKILL.md length
- 1,295 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Analyze the most expensive users in AI observability and explain why they cost so much.
- Works in 6 steps: Rank users by generated-call spend → Establish the baseline → Decompose the top user's cost drivers → …
- The user asks about top spenders
- SKILL.md covers Tools, Core rules, Workflow and Constructing UI links, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Analyzing Expensive Users is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Analyze the most expensive users in AI observability and explain why they cost so much. Use when the user asks about top spenders, expensive users, per-user LLM cost, user-level cost drivers, or patterns behind high AI observability spend.
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Observability and LLM cost and token optimization. It works with PostHog. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- The user asks about top spenders
- Expensive users
- Per-user LLM cost
- User-level cost drivers
Example prompts
- “/analyzing-expensive-users”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Rank users by generated-call spend
- Establish the baseline
- Decompose the top user's cost drivers
- Compare the top user against everyone else
- Find the user's expensive traces
- Check custom dimensions when the aggregate is ambiguous
What it can do on your machine
Read from SKILL.md and the folder at commit 10f9ad7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are sql and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyzing Expensive Users loads about 3.9k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 1,295 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,295 words (~3,858 tokens).
“Use this skill when the user wants to understand the most expensive users in AI observability. The job is not just to rank users by cost. The useful answer explains what makes the top users expensive: volume, model choice, prompt…”
- name
- analyzing-expensive-users
Files
Just SKILL.md in products/ai_observability/skills/analyzing-expensive-users of PostHog/posthog.
Open the folder on GitHubat commit 10f9ad7
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Analyzing Expensive Users next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyzing Expensive Users this skillPostHog/posthog | 40k | — | ~3.9k | Automated safety check: Pass | Custom licence | |
| Caveman Gateway SetupJuliusBrussee/caveman | 110k | 1 repos | ~2.6k | Automated safety check: Warn | Apache-2.0 | |
| Agent Kill Switchvivekchand/clawmetry | 425 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Clawmetry Selfcheckvivekchand/clawmetry | 425 | — | ~515 | Automated safety check: Pass | MIT | |
| Telemetry AnalyticsOpenHands/OpenHands | 90k | — | ~305 | Automated safety check: Pass | MIT | |
| Temps Best Practicesgotempsh/temps | 826 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Agent Kill Switch
vivekchand/clawmetry
Give the human an off switch and a cost meter for the coding agents on this machine, using ClawMetry.
Clawmetry Selfcheck
vivekchand/clawmetry
Read your own agent telemetry from ClawMetry (waste, progress, cost) and act on it before finishing a task.
Telemetry Analytics
OpenHands/OpenHands
This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts…
Temps Best Practices
gotempsh/temps
Best-practices reference for preparing and instrumenting applications on Temps.
Clawmetry
vivekchand/clawmetry
Real-time observability for OpenClaw agents — local dashboard + optional encrypted cloud sync.
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Categories
Questions about Analyzing Expensive Users
What does Analyzing Expensive Users do?
Analyze the most expensive users in AI observability and explain why they cost so much. Analyzing Expensive Users is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Analyze the most expensive users in AI observability and explain why they cost so much.
When should I use Analyzing Expensive Users?
Analyzing Expensive Users fits situations like: the user asks about top spenders; expensive users; per-user LLM cost; user-level cost drivers.
How do I install Analyzing Expensive Users in Claude Code?
Run `npx skills add PostHog/posthog --skill analyzing-expensive-users -a claude-code`. Or copy the skill folder (products/ai_observability/skills/analyzing-expensive-users in PostHog/posthog) into .claude/skills/analyzing-expensive-users in your project. Claude Code loads it when a task matches its description.
How do I install Analyzing Expensive Users in Codex?
Run `npx skills add PostHog/posthog --skill analyzing-expensive-users -a codex`. Or copy the skill folder (products/ai_observability/skills/analyzing-expensive-users in PostHog/posthog) into .agents/skills/analyzing-expensive-users in your project. Codex loads it when a task matches its description.
Can I use Analyzing Expensive Users in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill analyzing-expensive-users -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyzing-expensive-users, .gemini/skills/analyzing-expensive-users, .github/skills/analyzing-expensive-users and .opencode/skills/analyzing-expensive-users in your project.
What does Analyzing Expensive Users need to run?
SKILL.md names no scripts, command-line tools or credentials: Analyzing Expensive Users is instructions for the agent only.
Does Analyzing Expensive Users access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Analyzing Expensive Users safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Analyzing Expensive Users use?
Analyzing Expensive Users has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Analyzing Expensive Users use?
About 3.9k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Analyzing Expensive Users?
Skills that share tags, products or a category with Analyzing Expensive Users: Caveman Gateway Setup (JuliusBrussee/caveman, 110k stars), Agent Kill Switch (vivekchand/clawmetry, 425 stars), Clawmetry Selfcheck (vivekchand/clawmetry, 425 stars) and Telemetry Analytics (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyzing Expensive Users?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,182 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 8, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.