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 commands/mixpanel/ai-plugins/metric-driftgit clone --depth 1 https://github.com/mixpanel/ai-pluginsWrote 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/commands/mixpanel/ai-plugins/metric-drift)<a href="https://agentmods.dev/commands/mixpanel/ai-plugins/metric-drift"><img src="https://agentmods.dev/badge/commands/mixpanel/ai-plugins/metric-drift.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.03044 |
| Opus 5 | $0.00000 | $0.01522 |
| Sonnet 5 | $0.00000 | $0.00609 |
| Haiku 4.5 | $0.00000 | $0.00304 |
Grade A, and why
metric-drift 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 5d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: metric-drift
Detect trend-level drift in a single metric — whether the baseline itself has shifted over recent weeks. Produces a verdict on whether the metric is in a new regime. Does not test for point-in-time anomalies (run metric-anomaly for that).
Prerequisites
Before this command runs, Steps 0, 1, and 1.5 from references/execution.md must have completed — input validation, normalized metric series object, and project profile resolution. If any of those haven't happened, do them first.
If the user's input is a saved report but the metric is a funnel or retention report, see the "Special cases" section at the bottom.
Prerequisite — classify metric_type
Classify the metric per the metric_type table in SKILL.md and store metric_type on the series object before firing any queries.
Prerequisite — name the drift and baseline windows
The naming convention used throughout this command's output:
drift_window— the recent 30 days (most recent 30 days ending today).baseline_window— the prior 30 days (30 days ending 30 days before today).
Both windows are computed from Q1-daily. The weekly test uses 8 vs 8 weeks — those windows are reported alongside but are secondary to the daily windows for headline purposes.
Phase 1 — Fetch series (2 queries, parallel)
Fire both queries simultaneously:
| Query | Window | Granularity | Comparison |
|---|---|---|---|
| Q1-daily | Last 60 days | day |
Last 30 days vs. prior 30 days |
| Q1-weekly | Last 16 weeks | week |
Last 8 weeks vs. prior 8 weeks |
The 60-day daily view catches medium-term drift. The 16-week weekly view catches slow drift that the daily window would miss because daily noise drowns the signal. Running both is cheap and they answer different questions.
Use the query_template from the metric object; override only dateRange and unit (granularity). Do not re-apply filters — they're already baked in.
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.
- 5d ago First seen · 258 lines · 0 tokens per session scan A 504433c6c16b
metric-drift is a command published in the GitHub repository mixpanel/ai-plugins (15 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,044 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.