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/dashboard-inventorygit 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.00512 |
| Opus 5 | $0.00000 | $0.00256 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
dashboard-inventory 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 3d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: Dashboard Inventory
Lists all dashboards in a project with report counts, ownership, and metadata. Produces a governance-ready catalog. Read-only.
Execution
Phase 1 — Fetch all dashboards
Fetch the dashboard set per the Fetching the dashboard set rule, reusing dashboard_list_cache if it is already populated (e.g. from a prior cleanup command). Only re-fetch if the cache is empty.
Phase 2 — Enrich with layout data
For each dashboard, read its full layout. Fire in parallel (batches of 5).
Extract per dashboard:
- Report count: number of report cells
- Report names: the name of each report cell
- Text card count: number of text cells
- Row count
- Total cells
Cache layouts in dashboard_layout_cache.
Phase 3 — Build catalog
Present as a structured table:
Dashboard Inventory — [Project Name] ([project_id])
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ID | Title | Reports | Rows | Description
---------|---------------------------|---------|------|------------------
1234567 | Onboarding Funnel | 6 | 4 | Tracks new user...
1234568 | Product Health | 8 | 5 | Core KPIs for...
1234569 | Engagement Weekly | 4 | 3 | Weekly active...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total: 12 dashboards | 54 reports | Avg 4.5 reports/board
Phase 4 — Optional detail drill-down
After showing the catalog, if the user asks about a specific dashboard, show full details: all report names, description, text card contents. This data is already in dashboard_layout_cache — no additional calls needed.
Phase 5 — Optional export
If the user wants a downloadable version, offer to produce a Markdown or CSV file with the full catalog.
Output
The catalog table above, plus the summary line. Return control to router.
Error Handling
| Situation | Action |
|---|---|
| Fetch returns empty | "No dashboards in this project." Return. |
| Layout read fails for one board | Show row with "⚠️ Could not inspect" in Reports column |
| Large project (50+ dashboards) | Process in batches of 5, show progress: "Inspecting 15/52..." |
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.
- 3d ago First seen · 67 lines · 0 tokens per session scan A ec3c111883e4
dashboard-inventory is a command published in the GitHub repository mixpanel/ai-plugins (15 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 512 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.