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 analyze-chartgit 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/analyze-chart)<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/analyze-chart"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/analyze-chart/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/analyze-chart"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/analyze-chart.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.00046 | $0.00971 |
| Opus 5 | $0.00023 | $0.00485 |
| Sonnet 5 | $0.00009 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
analyze-chart 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 12d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chart Deep Dive
When to Use
- A metric spiked or dropped unexpectedly
- You need to understand what’s driving a trend
- Preparing a detailed, evidence-backed analysis for stakeholders
- Investigating differences between user or event segments
Instructions
Step 0: Identify the Chart
- Accept a chart URL or chart ID
- If the user provides a URL, use
Amplitude:get_from_urlto extract the chart ID - If no chart identifier is provided, ask explicitly for the chart URL or ID and stop
Step 1: Retrieve and Validate Chart Data (Mandatory)
- Use Reading chart data to retrieve the chart definition and data
- If chart data cannot be retrieved or is empty, do not proceed
- Explain what’s missing (time range, event, filters, permissions)
- Ask the user to correct the chart or provide a valid chart
Capture and restate:
- Metric being measured
- Time range and granularity
- Chart type (e.g. time series, funnel, retention)
- Existing filters, segments, or breakdowns
Step 2: Identify the Pattern and Change Window
Use Analyzing chart to characterize what’s happening:
- Spike / Drop: Sudden change on specific date(s)
- Trend: Gradual increase or decrease over time
- Seasonality: Recurring weekly or monthly patterns
- Anomaly: Deviation from recent baseline or historical behavior
Explicitly identify:
- The window of change (start/end)
- Direction and magnitude of the change
- Baseline period used for comparison (default: previous equal-length period)
Step 3: Investigate Likely Drivers (Bounded)
Instead of broad slicing, use guided segmentation:
- Use Finding the right event properties to identify the most relevant properties for explaining the change
- Select up to 9 high-signal properties (e.g. platform, country, plan, version)
- Re-run Analyzing chart with these properties in mind to determine:
- Which segments contribute most to the change
- Whether the pattern is localized or broad-based
- Only fetch up to 3 charts at a time when using
Amplitude:query_charts
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.
- 12d ago First seen · 128 lines · 46 tokens per session scan A ca25aab22468
analyze-chart is a skill published in the GitHub repository amplitude/mcp-marketplace (35 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 971 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…