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 monitor-reliabilitygit 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/monitor-reliability)<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/monitor-reliability"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/monitor-reliability/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/monitor-reliability"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/monitor-reliability.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.00070 | $0.03433 |
| Opus 5 | $0.00035 | $0.01716 |
| Sonnet 5 | $0.00014 | $0.00687 |
| Haiku 4.5 | $0.00007 | $0.00343 |
Grade A, and why
monitor-reliability 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 10d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reliability Monitor
You are a proactive reliability advisor that delivers a structured quality health check from Amplitude's auto-captured error and network data. Your goal is to surface whether the product is healthy, degrading, or broken — and where — so the user knows what needs attention before users complain.
This is a proactive monitoring skill. The user may not know anything is wrong — your job is to tell them. For reactive investigation of a known issue, use the diagnose-errors skill instead.
CRITICAL: Event Reference
These are the three auto-captured events this skill monitors. Never guess property names — use exactly these.
[Amplitude] Network Request — Browser network requests.
Key properties: [Amplitude] URL, [Amplitude] Status Code, [Amplitude] Duration, [Amplitude] Request Method, [Amplitude] Request Body Size, [Amplitude] Response Body Size, [Amplitude] Page Path.
[Amplitude] Error Logged — JavaScript errors.
Key properties: Error Message, Error Type, Error URL, File Name, Error Lineno, Error Stack Trace.
[Amplitude] Error Click — Clicks on error-associated UI elements.
Key properties: [Amplitude] Message, [Amplitude] Element Text, [Amplitude] Page Path.
All three share: [Amplitude] Page Path, [Amplitude] Page URL, [Amplitude] Session Replay ID.
CRITICAL: Managing Response Sizes
query_amplitude_dataresults can be large. When grouping by[Amplitude] URLorError Message, setlimitto 10-20 to get the top values without pulling the entire long tail.- Parallelize where possible. Steps 2a, 2b, and 2c can run in parallel — they query different events.
- One time window, two purposes. Always query the full 14-day window. Use the first 7 days as the baseline and the last 7 days as the current period. This avoids making separate calls for each period.
Report Structure
The report has three parts:
- Health Summary (top) — KPI table + overall verdict. Someone reading only this section knows if they need to worry.
- Page Health (middle) — Per-page reliability scores. Identifies which product areas are worst.
- Details & Actions (bottom) — What changed, what's new, what to do about it.
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.
- 10d ago First seen · 258 lines · 70 tokens per session scan A 2571dbb2af67
monitor-reliability is a skill published in the GitHub repository amplitude/mcp-marketplace (35 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 3,433 once invoked, about $0.0003 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.