Borrowing it
Nothing to install: this file belongs to PostHog/posthog-foss. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PostHog/posthog-foss/master/.agents/skills/documenting-warehouse-sources/SKILL.mdgit clone --depth 1 https://github.com/PostHog/posthog-fossWrote 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.
[](https://agentmods.dev/skills/posthog/posthog-foss/documenting-warehouse-sources)<a href="https://agentmods.dev/skills/posthog/posthog-foss/documenting-warehouse-sources"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/documenting-warehouse-sources/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.
<a href="https://agentmods.dev/skills/posthog/posthog-foss/documenting-warehouse-sources"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/documenting-warehouse-sources.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00095 | $0.01684 |
| Opus 5 | $0.00048 | $0.00842 |
| Sonnet 5 | $0.00019 | $0.00337 |
| Haiku 4.5 | $0.00010 | $0.00168 |
Grade A, and why
documenting-warehouse-sources 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documenting Data warehouse sources
User-facing source docs live in the posthog.com repo (not this one) at
contents/docs/cdp/sources/<slug>.md, served at both /docs/cdp/sources/<slug> and
/docs/data-warehouse/sources/<slug>. This skill defines the one consistent shape every source doc
must follow. Pair it with /implementing-warehouse-sources when shipping a new source.
Assume a sibling posthog.com checkout (e.g. ../posthog.com).
The two things the website renders for you
You do not hand-write connection fields or the table list — both come from the
public_source_configs API the site fetches at build time, mirrored into the doc via MDX components:
<SourceParameters />renders the connection/config form fields fromget_source_config.fields.<SourceTables />renders the Supported tables reference (table name, description, sync method, incremental field, primary key) from the source'sget_documented_tables().
<SourceTables /> only has data when the source opts in by setting
lists_tables_without_credentials = True on its source class (only valid when get_schemas iterates a
static endpoint catalog with no I/O — see /implementing-warehouse-sources). Otherwise it renders a
generic "discovered from your account" note. If a table is missing or its description is thin, fix the
source code (settings.py endpoints + canonical_descriptions.py), not the doc — the doc just renders
what the API returns, so the code stays the single source of truth.
Frontmatter
---
title: Linking <Source> as a source
sidebar: Docs
showTitle: true
availability: { free: full, selfServe: full, enterprise: full }
sourceId: <EnumValue> # MUST equal the ExternalDataSourceType value, e.g. ActiveCampaign, Stripe
beta: true # optional — only for beta sources
---
sourceId is what links the doc to its API config (icon, fields, tables). Get it wrong and the doc
renders with no <SourceParameters /> / <SourceTables /> data. It must be a real
ExternalDataSourceType value (PascalCase, e.g. ActiveCampaign, not Active Campaign).
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.
- 9d ago First seen · 159 lines · 95 tokens per session scan A 4acceabe2823
documenting-warehouse-sources is a skill published in the GitHub repository PostHog/posthog-foss (714 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 1,684 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…