migrate-posthog

A command for moving feature flags from PostHog to Confidence. Feature flags are settings that turn software features on or off for selected users.

In plain words
What is it for?
Use it when migrating a project's feature flags from PostHog to Confidence.
Why use it?
It provides a defined migration process for transferring those settings between the two services.

Command

Part of the confidence plugin — 13 skills, 17 commands, 2 MCP servers shipped together

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.

agentmods
npx agentmods add commands/spotify/confidence-ai-plugins/migrate-posthog
Clone the repo
git clone --depth 1 https://github.com/spotify/confidence-ai-plugins

Or install confidence, the plugin that ships this one along with the rest of its 13 skills, 17 commands, 2 MCP servers.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 91 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00015 $0.00091
Opus 5 $0.00008 $0.00046
Sonnet 5 $0.00003 $0.00018
Haiku 4.5 $0.00002 $0.00009

Measured 3d ago against content hash c8428524b18d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

migrate-posthog 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 3d 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.

commands/migrate-posthog.md · 10 lines

What it actually says

All migration instructions are maintained in skills/migrate-posthog/SKILL.md to prevent divergence.

Before doing anything else, use the Read tool to read skills/migrate-posthog/SKILL.md and follow those instructions to handle this command.

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. 3d ago First seen · 10 lines · 15 tokens per session scan A c8428524b18d

Subscribe to this mod's changes

migrate-posthog is a command published in the GitHub repository spotify/confidence-ai-plugins (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 91 once invoked, about $0.0001 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.