Official agent skill

Understanding Billing Usage

by PostHog in PostHog/posthog

Explains PostHog billing usage and spend from the customer's visible Billing MCP tools.

OfficialCustom licenceAuto-check passedProduct & Project Management

Install Understanding Billing Usage

skills CLI
$ npx skills add PostHog/posthog --skill understanding-billing-usage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PostHog/posthog understanding-billing-usage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/billing/skills/understanding-billing-usage .claude/skills/understanding-billing-usage && rm -rf skills-src

Use ~/.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/

Facts

Skill name
understanding-billing-usage
GitHub stars
40k
Token cost
~3.2k tokens
SKILL.md length
1,661 words
Files
3 (incl. references)
Skills in repo
252
Repo updated
First seen
Licence
Custom licence

At a glance

Explains PostHog billing usage and spend from the customer's visible Billing MCP tools.

  • Works in 6 steps: Classify the question → Recreate the Billing view → Attribute the usage → …
  • The user asks why usage
  • SKILL.md covers Available tools, Inputs to look for and Workflow
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Understanding Billing Usage is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey…

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/spike-alert-mechanics.md` and `references/usage-type-routing.md`).

It sits in Product & Project Management, covering MCP servers, Email management and Product metrics. It works with PostHog and Model Context Protocol. 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 why usage
  • Project is driving usage
  • What a usage type means
  • How to reduce usage

Example prompts

  • “Use the understanding-billing-usage skill to explain PostHog billing usage and spend from the customer's visible Billing MCP tools”
  • “/understanding-billing-usage”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Classify the question
  2. Recreate the Billing view
  3. Attribute the usage
  4. Apply alert-specific logic only for usage alerts
  5. Drill down through customer-visible product surfaces
  6. Answer in usage language

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).

    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

Understanding Billing Usage loads about 3.2k tokens when it runs, and up to ~7k if it reads all its reference files. Until then it costs about 182 tokens; SKILL.md has 1,661 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~182
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7k

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,661 words (~3,158 tokens).

“Use this skill for customer-facing "what am I using and why?" Billing usage workflows. The question may come from the Billing usage dashboard, a usage alert email, an AI chat prompt, or a user who noticed high usage, spend, a…”

— opening of SKILL.md by PostHog, Custom licence
name
understanding-billing-usage

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (references) in products/billing/skills/understanding-billing-usage of PostHog/posthog.

  • SKILL.md
  • references/spike-alert-mechanics.md
  • references/usage-type-routing.md

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

Understanding Billing Usage 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.

Understanding Billing Usage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Understanding Billing Usage this skillPostHog/posthog40k—~3.2kAutomated safety check: PassCustom licence
ObservalObserval/Observal4.2k—~2.2kAutomated safety check: PassApache-2.0
Jira Natural Language Interfacejjmartres/opencode1333 repos~1.7kAutomated safety check: PassMIT
Using Agent RelayAgentWorkforce/relay8661 repos~2kAutomated safety check: PassApache-2.0
Exploring The WizardPostHog/wizard197—~2.2kAutomated safety check: PassMIT
E2a Setuptokencanopy/e2a192—~820Automated safety check: PassApache-2.0

Similar skills

  • Observal

    Observal/Observal

    A skill your agent uses when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing…

    4.2k GitHub stars~2.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.

    133 GitHub starsUsed in 3 repos~1.7k tokens
    Product & Project ManagementAuto-check passed
  • Using Agent Relay

    AgentWorkforce/relay

    A skill your agent uses when you are a registered relay agent (a spawned worker, or a lead that called registeragent) coordinating with peers in real time over current Agent Relay MCP tools -…

    866 GitHub starsUsed in 1 repo~2k tokens
    Agent WorkflowsAuto-check passed
  • Exploring The Wizard

    PostHog/wizard

    Official

    Drive the PostHog wizard headlessly against a throwaway app through wizard-ci MCP tools, inspect decisions, and capture the real TUI.

    197 GitHub stars~2.2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • E2a Setup

    tokencanopy/e2a

    A skill your agent uses when a user wants to connect or authorize the e2a MCP server, select or create an agent inbox, verify first-run readiness, or set up a custom email domain.

    192 GitHub stars~820 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • Validate Harness

    ruvnet/metaharness

    Release-readiness umbrella check for a scaffolded harness — runs doctor, witness verify, hardcoded-path scan, MCP server config, and GCP Secret Manager validation in one shot.

    690 GitHub stars~372 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from PostHog/posthog

All 252 skills in this repo
  • Authoring Log Alerts

    PostHog/posthog

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    40k GitHub stars~3k tokensUpdated yesterday
    Auto-check passed
  • Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • Official

    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).

    40k GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Exploring Apm Traces

    PostHog/posthog

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    40k GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed
  • Exploring LLM Traces

    PostHog/posthog

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    40k GitHub stars~4.4k tokensUpdated yesterday
    Auto-check passed
  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    40k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

Questions about Understanding Billing Usage

What does Understanding Billing Usage do?

Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Understanding Billing Usage is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Explains PostHog billing usage and spend from the customer's visible Billing MCP tools.

When should I use Understanding Billing Usage?

Understanding Billing Usage fits situations like: the user asks why usage; project is driving usage; what a usage type means; how to reduce usage.

How do I install Understanding Billing Usage in Claude Code?

Run `npx skills add PostHog/posthog --skill understanding-billing-usage -a claude-code`. Or copy the skill folder (products/billing/skills/understanding-billing-usage in PostHog/posthog) into .claude/skills/understanding-billing-usage in your project. Claude Code loads it when a task matches its description.

How do I install Understanding Billing Usage in Codex?

Run `npx skills add PostHog/posthog --skill understanding-billing-usage -a codex`. Or copy the skill folder (products/billing/skills/understanding-billing-usage in PostHog/posthog) into .agents/skills/understanding-billing-usage in your project. Codex loads it when a task matches its description.

Can I use Understanding Billing Usage 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 understanding-billing-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/understanding-billing-usage, .gemini/skills/understanding-billing-usage, .github/skills/understanding-billing-usage and .opencode/skills/understanding-billing-usage in your project.

What does Understanding Billing Usage need to run?

SKILL.md names no scripts, command-line tools or credentials: Understanding Billing Usage is instructions for the agent only.

Does Understanding Billing Usage 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 Understanding Billing Usage 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 Understanding Billing Usage use?

Understanding Billing Usage 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 Understanding Billing Usage use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to Understanding Billing Usage?

Skills that share tags, products or a category with Understanding Billing Usage: Observal (Observal/Observal, 4.2k stars), Jira Natural Language Interface (jjmartres/opencode, 133 stars), Using Agent Relay (AgentWorkforce/relay, 866 stars) and Exploring The Wizard (PostHog/wizard, 197 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Understanding Billing Usage?

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.