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/update-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.00958 |
| Opus 5 | $0.00000 | $0.00479 |
| Sonnet 5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
update-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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: Update Dashboard
Modifies an existing dashboard's metadata, rows, or cell layout. The most flexible command — it handles renames, description edits, adding/removing rows, reordering rows, and updating cell content.
Contents
- Intake
- Execution (read layout → apply updates → confirm → execute & verify)
- Output
- Error Handling
Intake
Required:
- Dashboard ID — the board to update (accept by name or ID)
The user's intent determines the update path:
- Rename → title only
- Update description → description only
- Add a section/row → row + cell creation
- Remove a row → row deletion
- Reorder rows → row-order update
- Update a report cell → cell update with a new
query_id - Update a text card → cell update with new HTML
- Bulk restructure → a combination of the above
If the user doesn't specify a dashboard, help them find it using dashboard_list_cache or by fetching the set (per the Fetching the dashboard set rule).
Execution
Step 1 — Read current layout
Always start by reading the board's full layout, then show the user a structural summary so they can point at real rows/cells:
Dashboard: [Title] (ID: [dashboard_id])
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Row 1: [Report: "DAU Trend"] [Report: "WAU Trend"]
Row 2: [Text: "Engagement Section"]
Row 3: [Report: "Session Length"] [Report: "Retention"]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Layout cell/row IDs are opaque server-generated strings — read the real IDs from this layout; use temporary placeholder IDs only for newly-added rows/cells (see references/mcp-tool-reference.md).
Step 2 — Apply updates
Submit a single update to the board carrying the operations the user's intent requires. Work at the level of intent — consult the update tool's own schema for the exact operand order and payload shape.
| Intent | What to submit |
|---|---|
| Rename / edit description | Set the board's title and/or description. |
| Add a new row | One add-row operation. |
| Add a text card | An add-row operation plus a create-cell operation of type text carrying the card's HTML. |
| Add a report cell | First mint a query_id (run its query with results skipped), then an add-row op plus a create-cell op of type report referencing that query_id. |
| Delete a row or cell | A delete operation targeting the real server ID (read it from the layout first). |
| Update a text or report cell | An update operation targeting the real cell ID with the new HTML or new query_id. |
| Reorder rows | A set-row-order operation listing the real row IDs in the desired order. |
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 · 113 lines · 0 tokens per session scan A 353a57c19aba
update-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 958 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.
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.