migrating-llm-gateway-callers

migrating-llm-gateway-callers is a skill for Claude Code, Codex from PostHog/posthog-foss. It costs 102 tokens per session (1,101 once invoked), scanned A, original, MIT.

A guide for moving an application that calls a large-language-model service from PostHog’s old LLM gateway to its AI gateway. It covers the caller’s API, billing, authorization, model, streaming, and error-handling requirements.

In plain words
What is it for?
Use it when adding or migrating gateway callers, changing gateway URLs or headers, adopting shared client builders, or removing a Python fallback.
Why use it?
It helps identify whether the new gateway supports the caller’s existing behavior before changes are made, including Python fallbacks and usage limits.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it when adding or migrating gateway callers, changing gateway URLs or headers, adopting shared client builders, or removing a Python fallback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/posthog/posthog-foss/migrating-llm-gateway-callers
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add PostHog/posthog-foss --skill migrating-llm-gateway-callers
Clone the repo
git clone --depth 1 https://github.com/PostHog/posthog-foss

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for migrating-llm-gateway-callers

README.md
[![agentmods](https://agentmods.dev/badge/skills/posthog/posthog-foss/migrating-llm-gateway-callers/github.svg)](https://agentmods.dev/skills/posthog/posthog-foss/migrating-llm-gateway-callers)
Your own site
<a href="https://agentmods.dev/skills/posthog/posthog-foss/migrating-llm-gateway-callers"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/migrating-llm-gateway-callers/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for migrating-llm-gateway-callers

Your own site · 80×15
<a href="https://agentmods.dev/skills/posthog/posthog-foss/migrating-llm-gateway-callers"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/migrating-llm-gateway-callers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,101 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00102 $0.01101
Opus 5 $0.00051 $0.00550
Sonnet 5 $0.00020 $0.00220
Haiku 4.5 $0.00010 $0.00110

Measured 11d ago against content hash 05cf1ffa5007, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

migrating-llm-gateway-callers scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/migrating-llm-gateway-callers/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migrating LLM gateway callers

Use services/llm-gateway/PARITY.md as the current decision record. If it is stale or the migration reveals a new gap, run /auditing-llm-gateway-parity before continuing.

Inventory the caller

Find the production call site, client construction, settings, deployment wiring, and tests. Record:

  • caller and user-facing use case
  • credential source and required authorization policy
  • spend owner, budgets, current Python billing behavior, and the team wallet that should own Go spend
  • API shape, model, provider, streaming, and tool or structured-output requirements
  • distinct ID, trace, product, team, feature flag, and custom property attribution
  • timeout, retry, fallback, and error-handling behavior
  • usage or quota APIs read by the caller

Search for the product name, LLM_GATEWAY, AI_GATEWAY, gateway client helpers, and gateway headers. Follow configuration into sandbox or deployment code when the call does not run in Django.

Check whether migration is supported

Match every required contract to the parity record and current code.

  • If all required contracts are supported, continue with the migration.
  • If a 🔎 item applies, verify it against the caller's actual model, request, and configuration.
  • If a ⛔ gap applies, stop the migration. Report the exact blocker and keep the Python path.

An existing Python client or product route is not a blocker by itself.

Python's unbilled flag is not a blocker when an internal workload should debit a PostHog-owned team wallet for spend attribution. Confirm that the Go credential resolves to that team. Stop only when migration would charge a customer incorrectly, lose required customer budget policy, or violate a requirement to debit no wallet.

Implement the migration

Prefer the smallest existing pattern that matches the caller:

Read migration examples for verified PRs covering Django clients, staged workload rollout, sandbox wiring, and attribution continuity. Follow the contract demonstrated by the relevant example rather than copying its code mechanically.

Read the full file on GitHub · 84 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 84 lines · 102 tokens per session scan A 05cf1ffa5007

Subscribe to this mod's changes

migrating-llm-gateway-callers is a skill published in the GitHub repository PostHog/posthog-foss (715 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 1,101 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

gemini-api-agent-platform

Guides the usage of the Gemini API on Agent Platform with the Google Gen AI SDK for enterprise AI applications. Covers SDK usage (Python, JS/TS, Go, Java, C#), capabilities like Live API, tools, multimedia generation, caching, and batch prediction.

davila7/claude-code-templates · 61 tokens

open-source

Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…

browser-use/browser-use · 137 tokens

gemini-api-dev

Use this skill when writing code that calls the Gemini API for text generation, multi-turn chat, multimodal understanding, image generation, video generation, streaming responses, background research tasks, function calling, structured output, or migrating from the old generateContent API. Covers SDK usage and best…

google-gemini/gemini-skills · 73 tokens

deepstream-sop

Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…

NVIDIA/skills · 219 tokens

azure-search-documents-dotnet

Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: "Azure Search .NET"…

microsoft/skills · 102 tokens

azure-search-documents-ts

Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building agentic retrieval with knowledge bases.

microsoft/skills · 48 tokens