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/conventionsnpx skills add uptimerobot/ai --skill conventionsgit 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/conventions)<a href="https://agentmods.dev/skills/uptimerobot/ai/conventions"><img src="https://agentmods.dev/badge/skills/uptimerobot/ai/conventions.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.00057 | $0.00836 |
| Opus 5 | $0.00028 | $0.00418 |
| Sonnet 5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
conventions 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UptimeRobot conventions
Apply these rules whenever you use any tool from the uptimerobot MCP server (https://mcp.uptimerobot.com/mcp).
Monitor types
- Always pass
typeas a string enum — one ofHTTP,KEYWORD,PING,PORT,HEARTBEAT,DNS,API,UDP. Do not pass numeric type codes; the MCP layer rejects them. HEARTBEATmonitors must not include aurlon creation. The server generateshttps://heartbeat.uptimerobot.com/m<id>-<hash>and returns it. Show that URL to the user after creation so they can wire up the heartbeat sender.PING,PORT,UDP,DNS:urlis a hostname or IP, never a full URL with scheme.HTTP,KEYWORD,API:urlmust be a full URL with scheme (https://...).
Discovery before writes
- Before calling
update-monitor,update-monitor-status, or referencing a monitor by ID, calllist-monitors(optionally withsearch) to confirm the ID and current state. - Before referencing an alert contact in
assignedAlertContacts, calllist-integrationsand use anidfrom the response.
Verification after writes
- After
create-monitororupdate-monitor, callget-monitor-detailsto confirm the stored state before telling the user the change is live. Read-after-write replication can lag a few seconds.
Intervals and plan limits
- Interval is in seconds. Minimum is 30s and depends on the plan. If the server returns
-28002 subscription_limit_exceeded, do not retry — the plan cannot support that interval or monitor type. Tell the user. - Do not retry
-28001 monitor_limit_exceeded. Recommend deleting unused monitors or upgrading the plan. - Plans are Free, Solo, Team, Enterprise. Never reference a "Pro" or "Business" plan — neither exists.
Time ranges
timeRangeaccepts"24h","7d","30d"(range 1h–90d), or an ISO 8601 interval"<start>/<end>"(start before end, 1h–90d). Default is"7d".- For anything older than 90 days, inform the user that UptimeRobot's MCP endpoints cap at 90 days of history.
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 · 52 lines · 57 tokens per session scan A 374f432a0a6c
conventions is a skill published in the GitHub repository uptimerobot/ai (24 stars, last pushed 21d ago), licensed MIT. It adds 57 tokens to every session and 836 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
api-endpoints
Adding or changing API operations in @repo/operations. One source of truth (defineOperation + a Zod schema) becomes an HTTP endpoint, an OpenAPI operation, an MCP tool, TS + Python SDK methods, a latitude CLI command, and an in-process agent tool — descriptions and contracts must be written with all of these readers…
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.
web-frontend
When to use: apps/web UI — routes, @repo/ui, TanStack Start server functions and collections, navigation (Link vs useNavigate), forms (useForm with createFormSubmitHandler + fieldErrorsAsStrings when Zod validation errors should appear on fields), Tailwind layout rules, design-system updates, and useEffect /…
database-postgres
Drizzle schema, repositories, RLS, SqlClient wiring, Postgres migrations, psql / reset, or platform mappers (toDomain / toInsertRow).
notifications
Multi-channel notifications. Adding a new notification kind, group, or channel; in-app + email delivery; per-user prefs; project-level gates; idempotency.
async-jobs-and-events
Queues and workers, domain event publishers, async notifications or projections, or not doing that work inside HTTP handlers.