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 agentmods add skills/uptimerobot/ai/list-integrationsnpx skills add uptimerobot/ai --skill list-integrationsgit 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/list-integrations)<a href="https://agentmods.dev/skills/uptimerobot/ai/list-integrations"><img src="https://agentmods.dev/badge/skills/uptimerobot/ai/list-integrations.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00027 | $0.01012 |
| Opus 5 | $0.00014 | $0.00506 |
| Sonnet 5 | $0.00005 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
list-integrations 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List integrations
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.
Wraps the list-integrations MCP tool. Returns every alert-contact integration on the account — the destinations that can be attached to a monitor via assignedAlertContacts.
Use this whenever the user says "alert me on Slack", "page on-call", "email the team", etc. — you need the integration's numeric id before create-monitor or update-monitor will accept it.
Minimal call
{ "limit": 25 }
All parameters are optional:
limit— page size (clamped server-side).cursor— numeric cursor from the previous page'snextCursor.
Paginated. Follow the instructions field verbatim for the next call.
Response shape
{
"integrations": [
{
"id": 10,
"friendlyName": "Ops Slack",
"type": "Slack",
"status": "Active",
"enableNotificationsFor": "UpAndDown",
"sslExpirationReminder": true,
"value": "https://hooks.slack.com/services/..."
}
],
"currentPageCount": 1,
"totalCount": 1,
"nextCursor": null,
"hasMore": false,
"instructions": "This page contains 1 integrations. Total: 1. No more pages available"
}
Fields
id— numeric. Pass as a string toassignedAlertContacts[].alertContactIdoncreate-monitor/update-monitor.friendlyName— user-defined label. Use this when talking to the user; don't surface the rawvalue.type— one ofEmailToSms,Email,Webhook,PushBullet,Zapier,ProSms,Pushover,Slack,MobileAppOld,MobileApp,Voice,Splunk,PagerDuty,OpsGenie,Telegram,MSTeams,GoogleChat,Discord,Mattermost.status—NotActivated,Paused,Active,ToMigrate. OnlyActiveintegrations will actually deliver alerts.enableNotificationsFor—UpAndDown,Down,Up, orNone. IfNone, attaching it to a monitor won't produce alerts.value— the delivery target (email address, webhook URL, phone number). Treat as sensitive — don't echo it to the user unless they ask.
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.
- 3d ago First seen · 91 lines · 27 tokens per session scan A 637758b549d7
list-integrations is a skill published in the GitHub repository uptimerobot/ai (24 stars, last pushed 21d ago), licensed MIT. It adds 27 tokens to every session and 1,012 once invoked, about $0.0001 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
webhook-subscriptions
Webhook subscriptions: event-driven agent runs.
fix-datadog-issues
Find, triage, and fix production errors captured by Datadog Error Tracking, then open a PR. Use when asked to look at "Datadog issues/incidents/errors", "find and fix bugs from Datadog", investigate the most-frequent or newest production errors, or work a specific Datadog Error Tracking issue.
async-jobs-and-events
Queues and workers, domain event publishers, async notifications or projections, or not doing that work inside HTTP handlers.
effect-and-errors
Composing Effect programs, domain errors, HttpError, repository error types, or error propagation at HTTP boundaries.
ci-watchdog
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass. USE THIS SKILL when: The user wants to "keep an eye on CI" or "wait for checks to pass" The user mentions monitoring PR status, CI status, or GitHub checks The user asks to watch a PR until it's ready or fix failing checks…
gh-issue
Create clear, actionable GitHub issues for bugs, features, and improvements. Issues are primarily consumed by LLMs, so optimize for agent readability and actionability.