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 uptimerobot/ai --skill monitor-health-summarygit clone --depth 1 https://github.com/uptimerobot/aiWrote 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/uptimerobot/ai/monitor-health-summary)<a href="https://agentmods.dev/skills/uptimerobot/ai/monitor-health-summary"><img src="https://agentmods.dev/badge/skills/uptimerobot/ai/monitor-health-summary/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/uptimerobot/ai/monitor-health-summary"><img src="https://agentmods.dev/badge/skills/uptimerobot/ai/monitor-health-summary.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.01061 |
| Opus 5 | $0.00020 | $0.00531 |
| Sonnet 5 | $0.00008 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
monitor-health-summary 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor health summary
Preflight — read first. If you cannot see any
uptimerobot:*MCP tools in your tool list, invoke theuptimerobot:setupskill before doing anything else. Do not tell the user the MCP is misconfigured —setup's Step 0 detects the common case (server connected, tools loaded after session start) and resolves it without re-keying.
A fast overview of your monitoring account's current state. Combines account-wide stats, live down/paused lists, and recent incident activity into a single report.
Use this when the user asks "how's everything looking?", "give me a health check", "what's our monitoring status?", or "morning standup brief".
Step 1 — Account-wide snapshot
{ "timeRange": "24h" }
Call get-monitor-stats. Returns:
- Counts of monitors in each state (
up,down,paused,notStarted). - Overall uptime percentage across active monitors.
- Total incident count and downtime duration for the range.
- Plan-level monitor cap vs. current usage.
Adjust timeRange if the user wants a longer window (e.g. "7d" for a weekly brief).
Step 2 — List currently down monitors
{ "filter": ["DOWN"], "limit": 50 }
Paginate with cursor until hasMore: false. Collect each monitor's id and friendlyName and the timestamp from get-monitor-details if you need exact downtime duration.
If there are zero DOWN monitors, skip step 3 and say so clearly.
Step 3 — List paused monitors
{ "filter": ["PAUSED"], "limit": 50 }
Paginate until hasMore: false. You only need names and count — no need to fetch details for each.
Step 4 — Recent incidents
{ "timeRange": "24h", "limit": 25 }
Call list-incidents. Paginate until hasMore: false. Collect total count and sum of incident durations for the report footer.
Step 5 — Spot-check degraded monitors (optional)
For each DOWN monitor (limit to the top 3–5 by name if there are many), check response times to distinguish a full outage from degradation:
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 · 109 lines · 40 tokens per session scan A 5f503e9f3573
monitor-health-summary is a skill published in the GitHub repository uptimerobot/ai (24 stars, last pushed 27d ago), licensed MIT. It adds 40 tokens to every session and 1,061 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
aws-cloud-monitoring
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance. Use when checking AWS alarms, analyzing VPC flow logs, investigating network latency, or monitoring VPN and NAT Gateway metrics.
applicationinsights-setup
Sets up, migrates, or enhances Azure Monitor Application Insights in .NET applications. Detects application type and existing instrumentation automatically. Use when adding Application Insights, Azure Monitor, observability, or telemetry to ASP.NET Core, Worker Service, ASP.NET Classic, or Console apps, upgrading from…
system_status
Check system health -- disk usage, memory, running processes, uptime.
branch_health
Quick health check -- test counts and file stats for AIPass branches.
aws-collector-tool
AWS infrastructure collector. Fetches ECS status, CloudWatch logs, and metrics. Use when: checking ECS health, inspecting CloudWatch error logs, pulling infra metrics, or monitoring AWS resources.
monitoring
Use when setting up uptime and health monitoring, alerts, or on-call basics for a service already in production, so you learn it is down before customers do — health and readiness probes, alerting on SLO error-budget burn rather than raw counts, curing alert fatigue, on-call rotation with escalation, and a status…