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 manage-monitor-groupsgit 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/manage-monitor-groups)<a href="https://agentmods.dev/skills/uptimerobot/ai/manage-monitor-groups"><img src="https://agentmods.dev/badge/skills/uptimerobot/ai/manage-monitor-groups/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/manage-monitor-groups"><img src="https://agentmods.dev/badge/skills/uptimerobot/ai/manage-monitor-groups.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 85 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00033 | $0.01710 |
| Opus 5 | $0.00016 | $0.00855 |
| Sonnet 5 | $0.00007 | $0.00342 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
manage-monitor-groups 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage monitor groups
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.
UptimeRobot has two organizing mechanisms and they aren't interchangeable:
- Tags (
tagNameson a monitor, discovered vialist-tags) — free-form, many-per-monitor, no fixed ID, changeable any time viaupdate-monitor. - Monitor groups (
create-monitor-group/update-monitor-group/get-monitor-group/list-monitor-groups, requires themonitor-groupsplan feature) — one-per-monitor, has its own numeric ID, shows as a visual grouping on status pages.
Use this skill when the user says "organize my monitors", "put these into a group", "what should I tag this", or "set up groups for the status page".
The membership-is-invisible gotcha (read this first)
Group membership cannot be read back through any tool. create-monitor-group and update-monitor-group accept monitorIds/groupIds on write, but the response only ever contains id, name, createdAt, updatedAt — no monitor list. get-monitor-group and list-monitor-groups return the same shape. get-monitor-details on a monitor doesn't report a groupId either. There is currently no way to ask "which monitors are in this group" or "which group is this monitor in" over MCP — the dashboard is the only place to see it.
Practical consequences:
- If you assign monitors to a group, track the IDs yourself (chat context or a note) — none of
create-monitor-group,update-monitor-group,get-monitor-group, orlist-monitor-groupswill confirm it back to you directly. - Don't tell the user "group X contains monitors A, B, C" unless you were the one who just set that exact membership and haven't lost track of it.
- This is a strong practical reason to prefer tags over groups:
get-monitor-detailsdoes returntagsfor a monitor, so tag membership is always directly verifiable, unlike group membership.
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 · 94 lines · 33 tokens per session scan A b287375743f5
manage-monitor-groups is a skill published in the GitHub repository uptimerobot/ai (24 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,710 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
trulens-evaluation-setup
Configure feedback functions and selectors for TruLens evaluations.
trulens-instrumentation
Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimization.
trulens-diagnosis
Diagnose low evaluation scores and generate actionable improvement recommendations.
trulens-notebook-execution
Execute and display Jupyter notebooks for TruLens demos and quickstarts.
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
trulens-blocking-guardrails
Configure and use feedback functions as runtime blocking guardrails.