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/create-dashboardgit clone --depth 1 https://github.com/mixpanel/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.00000 | $0.00705 |
| Opus 5 | $0.00000 | $0.00352 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
create-dashboard 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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: Create Dashboard
Creates a new dashboard from a natural language description.
Intake
The user provides either:
- A description — e.g. "create a dashboard tracking onboarding funnel metrics"
- A structured spec — title, description, specific reports to include
Extract:
- Title (required) — infer from description if not stated
- Description (optional) — a 1-2 line summary
- Report intent (optional) — what charts/reports the user wants on the board
- Visibility — private or shared (default: shared)
- Time filter — if the user mentions a date range, set it; otherwise omit
Execution
Path A: Empty Dashboard (no reports specified or no query_ids available)
If the user just wants a board created without pre-built reports:
- Create the dashboard with the session
project_id, the extracted title and description, the chosen visibility, and at minimum one row holding a single text card, e.g.<h1>Dashboard Title</h1><p>Description here. Add reports to populate.</p>. - Return the dashboard ID and confirm.
Path B: Dashboard with Reports
If the user wants specific charts, each report needs a query_id minted first. The flow:
- For each desired report, run its query with results skipped to mint a
query_id. Read the query schema first if unsure about available events/properties. Fire queries in parallel where possible. - Assemble the rows, observing the layout limits and grouping rules in
references/mcp-tool-reference.md. Group related reports in the same row; use text cards as section headers between logical groups. - Create the dashboard with the assembled rows.
- Return the dashboard ID, title, and a summary of what was created.
Path C: Dashboard from a description (AI-inferred layout)
When the user gives a loose description like "build me a product health dashboard":
- Infer 4-8 logical report categories from the description.
- Create the dashboard with text-card section headers for each category and a placeholder description.
- Tell the user: "Created [Title] with section scaffolding. Reports need to be added manually or by minting queries — want me to populate any sections?"
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.
- 2d ago First seen · 84 lines · 0 tokens per session scan A e69a17820b2a
create-dashboard is a command published in the GitHub repository mixpanel/ai-plugins (15 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 705 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.