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.
npx agentmods add instructions/spotify/confidence-ai-plugins/claude-mdgit clone --depth 1 https://github.com/spotify/confidence-ai-pluginsWhat 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 | $0.00730 | $0.00730 |
| Opus 5 | $0.00365 | $0.00365 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
confidence-ai-plugins CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confidence Plugin
This plugin integrates Confidence with Claude Code, providing tools for feature flag management, experimentation, and migration from other platforms.
Commands
/confidence:migrate-posthog <plan flag | plan code | execute <plan-file>>— Migrate feature flags from PostHog to Confidence SDK/confidence:migrate-eppo <plan flag | plan code | execute <plan-file>>— Migrate feature flags from Eppo to Confidence SDK/confidence:migrate-statsig <plan flag | plan code | execute <plan-file>>— Migrate feature flags from Statsig to Confidence SDK/confidence:migrate-optimizely(no args →plan access) or/confidence:migrate-optimizely <plan access | adjust access | execute access | plan flags | adjust flags | execute flags | plan code | adjust code | execute code | execute <plan-file>>— Migrate Optimizely to Confidence. Phase 0–2 each support plan / adjust / execute; Flag clients are Step 4 ofplan access. See README — Optimizely → Confidence/confidence:onboard-confidence <create-account | invite-user | create-client | setup-wizard | setup-warehouse | learn | status>— Create accounts, onboard users, set up SDK clients, configure warehouses, and learn experimentation concepts/confidence:analyze-project [project-dir]— Analyze a project and propose meaningful feature flag changes using Confidence/confidence:instrument-events [project-dir]— Analyze a project, identify events to track, create event definitions with entity references, add SDK track() calls, and verify the pipeline/confidence:explore-metric [event-name or fact-table-name]— Generate a pre-filled Metric Explorer URL for any event or fact table to preview and create metrics in the UI
Skills
- migrate-posthog — Auto-triggers when the user asks to migrate PostHog flags or transform SDK code to Confidence
- migrate-eppo — Auto-triggers when the user asks to migrate Eppo flags or transform SDK code to Confidence
- migrate-statsig — Auto-triggers when the user asks to migrate Statsig gates/configs/experiments or transform SDK code to Confidence
- migrate-optimizely — Auto-triggers when the user asks to migrate or adjust Optimizely users, teams, groups, roles, policies, clients, flags/rollouts/experiments, or SDK code to Confidence (including adjust flags / adjust code)
- onboard-confidence — Auto-triggers when the user asks to create a Confidence account, invite users, set up SDK clients, configure warehouses, run the setup wizard, or learn about experimentation
- analyze-project — Auto-triggers when the user asks what to feature-flag, wants flag suggestions, or asks to analyze their project for feature flag opportunities
- instrument-events — Auto-triggers when the user asks to instrument events, add tracking, set up event tracking, analyze what to track, or measure experiment impact
- explore-metric — Auto-triggers when the user asks to explore a metric, preview a metric, create a metric from an event or fact table, or open the Metric Explorer
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.
- 3d ago First seen · 31 lines · 730 tokens per session scan A 0d1ac45d5802
confidence-ai-plugins CLAUDE.md is an instructions file published in the GitHub repository spotify/confidence-ai-plugins (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 730 tokens to every session, about $0.0036 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.