create-dashboard

A command that creates a dashboard from a written description or a structured specification. A dashboard is a page that groups charts, reports, and other information.

In plain words
What is it for?
Use it to create an empty dashboard or one prepared with specified reports and charts.
Why use it?
It removes the need to manually translate a request into dashboard details such as its title, visibility, time range, and reports.

Command

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/mixpanel/ai-plugins/create-dashboard
Clone the repo
git clone --depth 1 https://github.com/mixpanel/ai-plugins
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 705 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.00000 $0.00705
Opus 5 $0.00000 $0.00352
Sonnet 5 $0.00000 $0.00141
Haiku 4.5 $0.00000 $0.00071

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

Security

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.

plugins/mixpanel/skills/manage-boards/commands/create-dashboard.md · 84 lines

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:

  1. Title (required) — infer from description if not stated
  2. Description (optional) — a 1-2 line summary
  3. Report intent (optional) — what charts/reports the user wants on the board
  4. Visibility — private or shared (default: shared)
  5. 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:

  1. 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>.
  2. 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:

  1. 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.
  2. 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.
  3. Create the dashboard with the assembled rows.
  4. 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":

  1. Infer 4-8 logical report categories from the description.
  2. Create the dashboard with text-card section headers for each category and a placeholder description.
  3. Tell the user: "Created [Title] with section scaffolding. Reports need to be added manually or by minting queries — want me to populate any sections?"

Read the full file on GitHub · 84 lines

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. 2d ago First seen · 84 lines · 0 tokens per session scan A e69a17820b2a

Subscribe to this mod's changes

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.