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-rcagit 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-rca)<a href="https://agentmods.dev/commands/mixpanel/ai-plugins/metric-rca"><img src="https://agentmods.dev/badge/commands/mixpanel/ai-plugins/metric-rca.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.04738 |
| Opus 5 | $0.00000 | $0.02369 |
| Sonnet 5 | $0.00000 | $0.00948 |
| Haiku 4.5 | $0.00000 | $0.00474 |
Grade A, and why
metric-rca 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: metric-rca
Root-cause investigation for a flagged metric. Takes the diagnosis payload from a prior metric-anomaly or metric-drift run and fans out across a set of segmentation branches to localise where the movement concentrated. Produces a ranked list of findings and appends them to the diagnosis board the user already created.
This command does not re-run anomaly or drift detection. It assumes the movement has already been established — its job is attribution, not detection.
Prerequisites
Before this command runs, the session must hold a diagnosis payload in conversation memory from an earlier metric-anomaly or metric-drift run (see references/execution.md Step 2). The payload carries the project, metric, metric type, date ranges, flagged points or drift windows, and the query bodies used.
If no payload exists, do not attempt to run RCA from a cold start. Tell the user: "RCA runs on top of an existing anomaly or drift diagnosis. Run metric-anomaly or metric-drift first, then come back here." Stop.
Board state
If the user persisted the diagnosis as a Mixpanel board (Step 2 in references/execution.md), the payload will include diagnosis_board_id. This command appends to that board — it does not create a new one. If no board was created, skip the append step at the end and just return the findings inline; do not silently create a new board.
Ask once — business / market context
Before firing Branch 5, ask the user exactly once:
"What business or market is this metric tied to? (e.g., Indian e-commerce, Indian OTT streaming, SEA fintech.) I'll use this to check whether the flagged dates line up with festivals, launches, or category-specific events."
Hold the answer as business_context. If the user skips or says "not relevant", skip Branch 5 entirely — do not guess the market from project name or memory.
Phase 1 — Branch selection + parallel fan-out
Read the payload and decide which branches to run. Every branch runs against the same date ranges the source command used:
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 · 341 lines · 0 tokens per session scan A 3e5339c5ab91
metric-rca 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 4,738 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.