Omnibus Instrument LLM Analytics
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- Low risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to instrumenting AI applications with PostHog analytics. It guides developers through detecting their LLM stack, installing the necessary PostHog SDKs, and configuring wrappers or middleware to capture detailed telemetry for every LLM generation. By following provider-specific references, users can ensure consistent tracking of token counts, latency, and costs across a wide range of LLM providers and frameworks without altering their core application architecture.
What it does
- Detects existing LLM providers and frameworks in the codebase.
- Installs and configures the PostHog SDK for LLM observability.
- Instruments LLM calls to capture input/output tokens, latency, and costs.
- Associates LLM generations with specific user IDs for better tracking.
- Provides fallback manual capture methods for unsupported providers.
- Configures environment variables for secure API key management.
When to use it
- After implementing new LLM features in an application.
- When reviewing pull requests that introduce or modify AI model interactions.
- When you need to monitor token usage and costs for AI features.
- When setting up observability for a new AI-powered project.
Advantages
- Centralized visibility into AI model performance and costs.
- Minimal code changes required through wrapper-based instrumentation.
- Supports a broad ecosystem of LLM providers and frameworks.
- Enables user-level attribution for AI interactions.
- Maintains security by enforcing environment variable usage.
Usage examples
- “Instrument my existing Anthropic Claude implementation with PostHog analytics.”
- The agent will identify the Anthropic SDK usage, install the required PostHog packages, and wrap the client to automatically capture generation events.
- “Set up PostHog tracking for my AutoGen agents.”
- The agent will configure the PostHog OpenAI wrapper and integrate it into the AutoGen model client to start logging agentic LLM calls.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/omnibus-instrument-llm-analytics/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip omnibus-instrument-llm-analytics.zip -d .agents/skills
Documentation by PostHog
Add PostHog LLM analytics
Use this skill to add PostHog LLM analytics that trace AI model usage in new or changed code. Use it after implementing LLM features or reviewing PRs to ensure all generations are captured with token counts, latency, and costs. If PostHog is not yet installed, this skill also covers initial SDK setup. Supports any provider or framework.
Supported providers: OpenAI, Azure OpenAI, Anthropic, Google, Cohere, Mistral, Perplexity, DeepSeek, Groq, Together AI, Fireworks AI, xAI, Cerebras, Hugging Face, Ollama, OpenRouter.
Supported frameworks: LangChain, LlamaIndex, CrewAI, AutoGen, DSPy, LangGraph, Pydantic AI, Vercel AI, LiteLLM, Instructor, Semantic Kernel, Mirascope, Mastra, SmolAgents, OpenAI Agents.
Proxy/gateway: Portkey, Helicone.
Instructions
Follow these steps IN ORDER:
STEP 1: Analyze the codebase and detect the LLM stack.
Look for LLM provider SDKs (openai, anthropic, google-generativeai, etc.) and AI frameworks (langchain, llamaindex, crewai, etc.) in dependency files and imports.
Look for lockfiles to determine the package manager.
Check for existing PostHog or observability setup. If PostHog is already installed and LLM tracing is configured, skip to STEP 4 to add tracing for any new LLM calls.
STEP 2: Research instrumentation. (Skip if PostHog LLM tracing is already set up.) 2.1. Find the reference file below that matches the detected provider or framework — it is the source of truth for callback setup, middleware configuration, and event capture. Read it now. 2.2. If no reference matches, use manual-capture.md as a fallback — it covers the generic event capture approach that works with any provider.
STEP 3: Install the PostHog SDK. (Skip if PostHog is already set up.)
Add the PostHog SDK and any required callback/integration packages.
Do not manually edit dependency files — use the package manager's install command.
Always install packages as a background task. Don't await completion; proceed with other work immediately.
STEP 4: Add LLM tracing.
Instrument LLM calls to capture input tokens, output tokens, model name, latency, and costs for every generation.
Follow the provider-specific reference for the exact callback/middleware setup.
Do not alter the fundamental architecture of existing files. Make additions minimal and targeted.
You must read a file immediately before attempting to write it.
STEP 5: Link to users.
Associate LLM generations with identified users via distinct IDs when possible.
STEP 6: Set up environment variables.
If an env-file-tools MCP server is connected, use check_env_keys then set_env_values to configure the PostHog API key and host.
Reference these environment variables in code instead of hardcoding them.
Reference files
references/openai.md- Openai llm analytics installation - docsreferences/azure-openai.md- Azure openai llm analytics installation - docsreferences/anthropic.md- Anthropic llm analytics installation - docsreferences/google.md- Google llm analytics installation - docsreferences/cohere.md- Cohere llm analytics installation - docsreferences/mistral.md- Mistral llm analytics installation - docsreferences/perplexity.md- Perplexity llm analytics installation - docsreferences/deepseek.md- Deepseek llm analytics installation - docsreferences/groq.md- Groq llm analytics installation - docsreferences/together-ai.md- Together ai llm analytics installation - docsreferences/fireworks-ai.md- Fireworks ai llm analytics installation - docsreferences/xai.md- Xai llm analytics installation - docsreferences/cerebras.md- Cerebras llm analytics installation - docsreferences/hugging-face.md- Hugging face llm analytics installation - docsreferences/ollama.md- Ollama llm analytics installation - docsreferences/openrouter.md- Openrouter llm analytics installation - docsreferences/langchain.md- Langchain llm analytics installation - docsreferences/llamaindex.md- Llamaindex llm analytics installation - docsreferences/crewai.md- Crewai llm analytics installation - docsreferences/autogen.md- Autogen llm analytics installation - docsreferences/dspy.md- Dspy llm analytics installation - docsreferences/langgraph.md- Langgraph llm analytics installation - docsreferences/pydantic-ai.md- Pydantic ai llm analytics installation - docsreferences/vercel-ai.md- Vercel ai SDK llm analytics installation - docsreferences/litellm.md- Litellm llm analytics installation - docsreferences/instructor.md- Instructor llm analytics installation - docsreferences/semantic-kernel.md- Semantic kernel llm analytics installation - docsreferences/mirascope.md- Mirascope llm analytics installation - docsreferences/mastra.md- Mastra llm analytics installation - docsreferences/smolagents.md- Smolagents llm analytics installation - docsreferences/openai-agents.md- Openai agents SDK llm analytics installation - docsreferences/portkey.md- Portkey llm analytics installation - docsreferences/helicone.md- Helicone llm analytics installation - docsreferences/manual-capture.md- Manual capture llm analytics installation - docsreferences/basics.md- Llm analytics basics - docsreferences/traces.md- Traces - docsreferences/calculating-costs.md- Calculating llm costs - docs
Each provider reference contains installation instructions, SDK setup, and code examples specific to that provider or framework. Find the reference that matches the user's stack.
If the user's provider isn't listed, use manual-capture.md as a fallback — it covers the generic event capture approach that works with any provider.
Key principles
Environment variables: Always use environment variables for PostHog and LLM provider keys. Never hardcode them.
Minimal changes: Add LLM analytics alongside existing LLM calls. Don't replace or restructure existing code.
Trace all generations: Capture input tokens, output tokens, model name, latency, and costs for every LLM call.
Link to users: Associate LLM generations with identified users via distinct IDs when possible.
One provider at a time: Only instrument the provider(s) the user is actually using. Don't add instrumentation for providers not present in the codebase.
Files
- ATTRIBUTION.mdAdded by AutoGineer966 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md6.6 KiB
- references/anthropic.md6.6 KiB
- references/autogen.md4.5 KiB
- references/azure-openai.md6.4 KiB
- references/basics.md3.2 KiB
- references/calculating-costs.md8.3 KiB
- references/cerebras.md6.7 KiB
- references/cohere.md6.7 KiB
- references/crewai.md4.4 KiB
- references/deepseek.md6.7 KiB
- references/dspy.md4.4 KiB
- references/fireworks-ai.md6.8 KiB
- references/google.md7.6 KiB
- references/groq.md6.7 KiB
- references/helicone.md6.9 KiB
- references/hugging-face.md6.8 KiB
- references/instructor.md5.8 KiB
- references/langchain.md6.9 KiB
- references/langgraph.md6.6 KiB
- references/litellm.md6.6 KiB
- references/llamaindex.md4.7 KiB
- references/manual-capture.md15.6 KiB
- references/mastra.md5.1 KiB
- references/mirascope.md4.5 KiB
- references/mistral.md6.7 KiB
- references/ollama.md6.7 KiB
- references/openai-agents.md5.7 KiB
- references/openai.md6.2 KiB
- references/openrouter.md7.1 KiB
- references/perplexity.md6.7 KiB
- references/portkey.md7.0 KiB
- references/pydantic-ai.md4.5 KiB
- references/semantic-kernel.md4.5 KiB
- references/smolagents.md4.3 KiB
- references/together-ai.md6.7 KiB
- references/traces.md5.8 KiB
- references/vercel-ai.md4.5 KiB
- references/xai.md6.6 KiB
references/manual-capture.md
Manual capture LLM analytics installation - Docs
1
Capture LLM events manually
If you're using a different server-side SDK or prefer to use the API, you can manually capture the data by calling the
capturemethod or using the capture API.API
Capture via API
curl -X POST "https://us.i.posthog.com/i/v0/e/" \ -H "Content-Type: application/json" \ -d '{ "api_key": "<ph_project_token>", "event": "$ai_generation", "properties": { "distinct_id": "user_123", "$ai_trace_id": "trace_id_here", "$ai_model": "gpt-5-mini", "$ai_provider": "openai", "$ai_input": [{"role": "user", "content": "Tell me a fun fact about hedgehogs"}], "$ai_input_tokens": 10, "$ai_output_choices": [{"role": "assistant", "content": "Hedgehogs have around 5,000 to 7,000 spines on their backs!"}], "$ai_output_tokens": 20, "$ai_latency": 1.5, "$ai_stream": true, "$ai_time_to_first_token": 0.25 } }'Node.js
1. Install
npm install posthog-node2. Initialize PostHog
import { PostHog } from 'posthog-node' const client = new PostHog('<ph_project_token>', { host: 'https://us.i.posthog.com' })3. Capture Event
// After your LLM call client.capture({ distinctId: 'user_123', event: '$ai_generation', properties: { $ai_trace_id: 'trace_id_here', $ai_model: 'gpt-5-mini', $ai_provider: 'openai', $ai_input: [{ role: 'user', content: 'Tell me a fun fact about hedgehogs' }], $ai_input_tokens: 10, $ai_output_choices: [{ role: 'assistant', content: 'Hedgehogs have around 5,000 to 7,000 spines on their backs!' }], $ai_output_tokens: 20, $ai_latency: 1.5, // For streaming responses, also include: // $ai_stream: true, // $ai_time_to_first_token: 0.25 } }) client.shutdown()Python
1. Install
pip install posthog2. Initialize PostHog
from posthog import Posthog posthog = Posthog("<ph_project_token>", host="https://us.i.posthog.com")3. Capture Event
# After your LLM call posthog.capture( distinct_id='user_123', event='$ai_generation', properties={ '$ai_trace_id': 'trace_id_here', '$ai_model': 'gpt-5-mini', '$ai_provider': 'openai', '$ai_input': [{'role': 'user', 'content': 'Tell me a fun fact about hedgehogs'}], '$ai_input_tokens': 10, '$ai_output_choices': [{'role': 'assistant', 'content': 'Hedgehogs have around 5,000 to 7,000 spines on their backs!'}], '$ai_output_tokens': 20, '$ai_latency': 1.5, # For streaming responses, also include: # '$ai_stream': True, # '$ai_time_to_first_token': 0.25 } )Go
1. Install
go get github.com/posthog/posthog-go2. Initialize PostHog
import "github.com/posthog/posthog-go" client, _ := posthog.NewWithConfig("<ph_project_token>", posthog.Config{ Endpoint: "https://us.i.posthog.com", }) defer client.Close()3. Capture Event
// After your LLM call client.Enqueue(posthog.Capture{ DistinctId: "user_123", Event: "$ai_generation", Properties: map[string]interface{}{ "$ai_trace_id": "trace_id_here", "$ai_model": "gpt-5-mini", "$ai_provider": "openai", "$ai_input_tokens": 10, "$ai_output_tokens": 20, "$ai_latency": 1.5, // For streaming responses, also include: // "$ai_stream": true, // "$ai_time_to_first_token": 0.25, }, })Ruby
1. Install
gem install posthog-ruby2. Initialize PostHog
require 'posthog-ruby' posthog = PostHog::Client.new({ api_key: '<ph_project_token>', host: 'https://us.i.posthog.com' })3. Capture Event
# After your LLM call posthog.capture({ distinct_id: 'user_123', event: '$ai_generation', properties: { '$ai_trace_id' => 'trace_id_here', '$ai_model' => 'gpt-5-mini', '$ai_provider' => 'openai', '$ai_input_tokens' => 10, '$ai_output_tokens' => 20, '$ai_latency' => 1.5 # For streaming responses, also include: # '$ai_stream' => true, # '$ai_time_to_first_token' => 0.25 } })PHP
1. Install
composer require posthog/posthog-php2. Initialize PostHog
<?php require_once __DIR__ . '/vendor/autoload.php'; use PostHog\PostHog; PostHog::init('<ph_project_token>', [ 'host' => 'https://us.i.posthog.com' ]);3. Capture Event
// After your LLM call PostHog::capture([ 'distinctId' => 'user_123', 'event' => '$ai_generation', 'properties' => [ '$ai_trace_id' => 'trace_id_here', '$ai_model' => 'gpt-5-mini', '$ai_provider' => 'openai', '$ai_input_tokens' => 10, '$ai_output_tokens' => 20, '$ai_latency' => 1.5 // For streaming responses, also include: // '$ai_stream' => true, // '$ai_time_to_first_token' => 0.25 ] ]);Event Properties
Each event type has specific properties. See the tabs below for detailed property documentation for each event type.
Generation
A generation is a single call to an LLM.
Event name:
$ai_generationCore properties
Property Description $ai_trace_id The trace ID (a UUID to group AI events) like conversation_idMust contain only letters, numbers, and special characters: -, _, ~, ., @, (, ), !, ', :, |Example: d9222e05-8708-41b8-98ea-d4a21849e761 $ai_session_id (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 $ai_span_id (Optional) Unique identifier for this generation $ai_span_name (Optional) Name given to this generationExample: summarize_text $ai_parent_id (Optional) Parent span ID for tree view grouping $ai_model The model usedExample: gpt-5-mini $ai_provider The LLM providerExample: openai, anthropic, gemini $ai_input_tokens The number of tokens in the input (often found in response.usage) $ai_output_tokens The number of tokens in the output (often found in response.usage) $ai_latency (Optional) The latency of the LLM call in seconds $ai_time_to_first_token (Optional) Time to first token in seconds. Only applicable for streaming responses. $ai_http_status (Optional) The HTTP status code of the response $ai_base_url (Optional) The base URL of the LLM providerExample: https://api.openai.com/v1 $ai_request_url (Optional) The full URL of the request made to the LLM APIExample: https://api.openai.com/v1/chat/completions $ai_is_error (Optional) Boolean to indicate if the request was an error $ai_error (Optional) The error message or object Cost properties
Cost properties are optional as we can automatically calculate them from model and token counts. If you want, you can provide your own cost properties or custom pricing instead.
Pre-calculated costs
Property Description $ai_input_cost_usd (Optional) The cost in USD of the input tokens $ai_output_cost_usd (Optional) The cost in USD of the output tokens $ai_request_cost_usd (Optional) The cost in USD for the requests $ai_web_search_cost_usd (Optional) The cost in USD for the web searches $ai_total_cost_usd (Optional) The total cost in USD (sum of all cost components) Custom pricing
Property Description $ai_input_token_price (Optional) Price per input token (used to calculate $ai_input_cost_usd) $ai_output_token_price (Optional) Price per output token (used to calculate $ai_output_cost_usd) $ai_cache_read_token_price (Optional) Price per cached token read $ai_cache_write_token_price (Optional) Price per cached token write $ai_request_price (Optional) Price per request $ai_request_count (Optional) Number of requests (defaults to 1 if $ai_request_price is set) $ai_web_search_price (Optional) Price per web search $ai_web_search_count (Optional) Number of web searches performed Cache properties
Property Description $ai_cache_read_input_tokens (Optional) Number of tokens read from cache $ai_cache_creation_input_tokens (Optional) Number of tokens written to cache (Anthropic-specific) $ai_cache_reporting_exclusive (Optional) Whether cache tokens are excluded from $ai_input_tokens. When true, cache tokens are separate from input tokens. When false, input tokens already include cache tokens. Defaults to true for Anthropic provider or Claude models, false otherwise. Model parameters
Property Description $ai_temperature (Optional) Temperature parameter used in the LLM request $ai_stream (Optional) Whether the response was streamed $ai_max_tokens (Optional) Maximum tokens setting for the LLM response Trace
A trace is a group that contains multiple spans, generations, and embeddings. Traces can be manually sent as events or appear as pseudo-events automatically created from child events.
Event name:
$ai_traceCore properties
Property Description $ai_trace_id The trace ID (a UUID to group related AI events together)Must contain only letters, numbers, and special characters: -, _, ~, ., @, (, ), !, ', :, |Example: d9222e05-8708-41b8-98ea-d4a21849e761 $ai_session_id (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 $ai_latency (Optional) The latency of the trace in seconds $ai_span_name (Optional) The name of the traceExample: chat_completion, rag_pipeline $ai_is_error (Optional) Boolean to indicate if the trace encountered an error $ai_error (Optional) The error message or object if the trace failed Pseudo-trace Events
When you send generation (
$ai_generation), span ($ai_span), or embedding ($ai_embedding) events with a$ai_trace_id, PostHog automatically creates a pseudo-trace event that appears in the dashboard as a parent grouping. These pseudo-traces:Are not actual events in your data
Automatically aggregate metrics from child events (latency, tokens, costs)
Provide a hierarchical view of your AI operations
Do not require sending an explicit
$ai_traceevent
This means you can either:
Send explicit
$ai_traceevents to control the trace metadataLet PostHog automatically create pseudo-traces from your generation/span events
Span
A span is a single action within your application, such as a function call or vector database search.
Event name:
$ai_spanCore properties
Property Description $ai_trace_id The trace ID (a UUID to group related AI events together)Must contain only letters, numbers, and the following characters: -, _, ~, ., @, (, ), !, ', :, |Example: d9222e05-8708-41b8-98ea-d4a21849e761 $ai_session_id (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 $ai_span_id (Optional) Unique identifier for this spanExample: bdf42359-9364-4db7-8958-c001f28c9255 $ai_span_name (Optional) The name of the spanExample: vector_search, data_retrieval, tool_call $ai_parent_id (Optional) Parent ID for tree view grouping (trace_id or another span_id)Example: 537b7988-0186-494f-a313-77a5a8f7db26 $ai_latency (Optional) The latency of the span in secondsExample: 0.361 $ai_is_error (Optional) Boolean to indicate if the span encountered an error Embedding
An embedding is a single call to an embedding model to convert text into a vector representation.
Event name:
$ai_embeddingCore properties
Property Description $ai_trace_id The trace ID (a UUID to group related AI events together). Must contain only letters, numbers, and special characters: -, _, ~, ., @, (, ), !, ', :, |Example: d9222e05-8708-41b8-98ea-d4a21849e761 $ai_session_id (Optional) Groups related traces together. Use this to organize traces by whatever grouping makes sense for your application (user sessions, workflows, conversations, or other logical boundaries).Example: session-abc-123, conv-user-456 $ai_span_id (Optional) Unique identifier for this embedding operation $ai_span_name (Optional) Name given to this embedding operationExample: embed_user_query, index_document $ai_parent_id (Optional) Parent span ID for tree-view grouping $ai_model The embedding model usedExample: text-embedding-3-small, text-embedding-ada-002 $ai_provider The LLM providerExample: openai, cohere, voyage $ai_input The text to embedExample: "Tell me a fun fact about hedgehogs" or array of strings for batch embeddings $ai_input_tokens The number of tokens in the input $ai_latency (Optional) The latency of the embedding call in seconds $ai_http_status (Optional) The HTTP status code of the response $ai_base_url (Optional) The base URL of the LLM providerExample: https://api.openai.com/v1 $ai_request_url (Optional) The full URL of the request made to the embedding APIExample: https://api.openai.com/v1/embeddings $ai_is_error (Optional) Boolean to indicate if the request was an error $ai_error (Optional) The error message or object if the embedding failed Cost properties
Cost properties are optional as we can automatically calculate them from model and token counts. If you want, you can provide your own cost property instead.
Property Description $ai_input_cost_usd (Optional) Cost in USD for input tokens $ai_output_cost_usd (Optional) Cost in USD for output tokens (usually 0 for embeddings) $ai_total_cost_usd (Optional) Total cost in USD
Community questions
Ask a question
Was this page useful?
HelpfulCould be better
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs an API key
Security
What our scanner noticed· Low risk
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- PostHog
- Publisher
- PostHog (Official)
- Source
- PostHog/skills · skills/posthog/llm-analytics/skills/all · commit a5d30e7
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- PostHog/skills
AutoGineer is not affiliated with or endorsed by PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omnibus-instrument-llm-analytics.zip