agentmods.dev

ai AGENTS.md

A repository guide for UptimeRobot, a service that checks websites, APIs, servers, DNS, and other services and reports when they go down.

In plain words
What is it for?
Use it to create, inspect, and control monitors, configure alert destinations, review downtime incidents, label monitors, and schedule periods when alerts are suppressed.
Why use it?
It explains the service’s monitors, incidents, alerts, tags, and maintenance windows so an agent can manage monitoring correctly.

Instructions file for CodexOpenCode

24 20d ago A scan 3,110 tokens original MIT
View the source file uptimerobot/ai
Install

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.

agentmods
npx agentmods add instructions/uptimerobot/ai/agents-md
Clone the repo
git clone --depth 1 https://github.com/uptimerobot/ai

Made for: Codex, OpenCode.

Per session 3,110 This file is loaded in full into every session.
When invoked 3,110 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.03110 $0.03110
Opus 5 $0.01555 $0.01555
Sonnet 5 $0.00622 $0.00622
Haiku 4.5 $0.00311 $0.00311

Measured 2d ago against content hash ad6c2bf288de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ai AGENTS.md 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 2d 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.

AGENTS.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — UptimeRobot

Orientation for coding agents (Claude Code, Cursor, Codex, Aider, etc.) that need to create, inspect, or control UptimeRobot monitors on a user's behalf.

What UptimeRobot is

UptimeRobot monitors websites, APIs, servers, DNS, and services. It probes each target on an interval (minimum 30s on paid plans), records up/down state plus response times, opens incidents on downtime, and fires alerts (email, SMS, webhooks, Slack, etc.) through alert contacts.

Key entities:

  • Monitor — one probe against one target. Has a type (HTTP, KEYWORD, PING, PORT, HEARTBEAT, DNS, API, UDP), a URL/host, an interval, and a status (UP, DOWN, PAUSED, NOT_STARTED, etc.).
  • Incident — a downtime event. Opens when a monitor goes down, closes when it recovers. Has logs, checker IPs, traceroute.
  • Alert contact — a destination (email, Slack, webhook, SMS, Telegram, etc.) attached to monitors with a threshold and recurrence.
  • Tag — free-form label assigned to monitors.
  • Maintenance window — scheduled period where alerts for attached monitors are suppressed.

Plans: Free, Solo, Team, Enterprise. Availability of specific monitor types and minimum intervals depends on the active plan. The MCP server enforces all limits.

How to talk to UptimeRobot

Use the remote MCP server:

  • URL: https://mcp.uptimerobot.com/mcp
  • Transport: HTTP (streamable), launched via mcp-remote (npx -y mcp-remote@latest https://mcp.uptimerobot.com/mcp).
  • Auth: OAuth. On first connection mcp-remote opens a browser to log into UptimeRobot and authorize — no API key to paste. (For headless/CI where a browser can't run, connect over plain HTTP with an Authorization: Bearer <API_KEY> header instead.)

All 32 tools operate on the authorized account. There is no account impersonation.

First-time setup (Claude Code, Cursor, or any MCP client): see skills/setup/SKILL.md.

No account? Create a monitor with just an email

Read the full file on GitHub · 172 lines

Changes

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.

  1. 2d ago First seen · 172 lines · 3,110 tokens per session scan A ad6c2bf288de

Subscribe to this mod's changes

ai AGENTS.md is an instructions file published in the GitHub repository uptimerobot/ai (24 stars, last pushed 20d ago), licensed MIT. It adds 3,110 tokens to every session, about $0.0155 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.

ai-integrationsai-monitoringuptimeuptime-monitoringuptime-robotuptimerobot
Related

Other instructions, from other repositories

trulens AGENTS.md

AGENTS.md instructions for truera/trulens, covering agents.md, setup commands, code style, testing instructions and test markers.

truera/trulens · 2,825 tokens

latitude-llm AGENTS.md

AGENTS.md instructions for latitude-dev/latitude-llm, covering agents.md, product scope, repo-wide conventions, how to use this guide and skill glossary.

latitude-dev/latitude-llm · 4,006 tokens

phoenix AGENTS.md

AGENTS.md instructions for Arize-ai/phoenix, covering agent instructions, build & development and python dependency version policy.

Arize-ai/phoenix · 189 tokens

phoenix CLAUDE.md

Claude Code instructions for Arize-ai/phoenix, a project described as: AI Observability & Evaluation.

Arize-ai/phoenix · 3 tokens

kuvasz AGENTS.md

AGENTS.md instructions for kuvasz-uptime/kuvasz, covering tech stack, key rules for contributing to the project, important commands and code style guidelines.

kuvasz-uptime/kuvasz · 711 tokens

latitude-llm CLAUDE.md

Claude Code instructions for latitude-dev/latitude-llm, a project described as: Latitude is the open-source AI monitoring platform.

latitude-dev/latitude-llm · 3 tokens