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 skills add amplitude/mcp-marketplace --skill create-dashboardgit clone --depth 1 https://github.com/amplitude/mcp-marketplaceWrote 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/skills/amplitude/mcp-marketplace/create-dashboard)<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/create-dashboard"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/create-dashboard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/create-dashboard"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/create-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00040 | $0.00844 |
| Opus 5 | $0.00020 | $0.00422 |
| Sonnet 5 | $0.00008 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00084 |
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 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Dashboard
Create new team or initiative dashboards, organize scattered charts, build executive reporting, or set up review cadence dashboards.
Instructions
Step 0: Discovery (if unfamiliar with the feature)
Before building, understand what you're tracking:
- Search for existing dashboards/charts related to the topic
- Inspect the connected catalog and use its taxonomy search/read capabilities to find relevant events and segmentation properties; never guess names or scopes
- Ask user for clarification on primary goals, key segments, or time horizons
Step 1: Define Dashboard Purpose
Clarify:
- Who is the audience?
- What decisions will it inform?
- How frequently will it be reviewed?
- What's the narrative structure?
Step 2: Gather or Create Charts
If existing charts found (>5 relevant):
- Use
Amplitude:search_amp_entitiesto find relevant existing charts - Use
Amplitude:get_amplitude_chartswithinclude: "definition"to retrieve their definitions - Identify gaps that need new charts
If few/no charts exist (<5 relevant):
- Switch to "greenfield build" mode
- Use
Amplitude:query_amplitude_datato create needed charts - Keep the returned chart edit IDs;
use_amp_dashboardspromotes them when creating the dashboard - Consider searching for relevant events first with entityTypes: ["EVENT", "CUSTOM_EVENT"]
Creating new charts:
- Prototype with
query_amplitude_datato verify data - Collect the returned chart edit IDs before creating the dashboard
Step 3: Plan the Layout
Organize into logical sections:
- Summary Row: Key metrics at a glance (headline view)
- Trend Section: How things are changing
- Breakdown Section: Segments and dimensions
- Detail Section: Supporting analyses
Step 4: Create the Dashboard
Use Amplitude:use_amp_dashboards with action: "create" and:
- Clear, descriptive name
- Rows with appropriate heights (375, 500, 625, or 750px)
- Charts sized appropriately (3-12 columns)
- Rich text headers for sections
- Chart display configurations in chartMetas:
metric_only: Headline KPIs (single number)series: Trend lines (default view)converted: Funnels (conversion view)table: Data tables
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 Changed 5b244a4f8132
- 11d ago First seen · 111 lines · 40 tokens per session scan A 5027e32ef73d
create-dashboard is a skill published in the GitHub repository amplitude/mcp-marketplace (35 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 844 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…