create-keyword-monitor

create-keyword-monitor is a skill for Claude Code from uptimerobot/ai. It costs 32 tokens per session (733 once invoked), scanned A, original, MIT.

A monitor that fetches a web URL and checks whether a chosen keyword appears in the response. It can alert when expected text disappears or when an error message appears.

In plain words
What is it for?
Use it to watch web pages for required or unwanted text. It is suited to checks such as confirming that a login page still shows “Sign in” or that “502 Bad Gateway” is absent.
Why use it?
It detects content problems that a simple check for a successful web response would miss. For example, it can notice a missing sign-in label or a visible server-error message.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the uptimerobot plugin — 24 skills, 1 MCP server shipped together

Good fit Use it to watch web pages for required or unwanted text. It is suited to checks such as confirming that a login page still shows “Sign in” or that “502 Bad Gateway” is absent.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uptimerobot/ai/create-keyword-monitor
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.

Any agent
npx skills add uptimerobot/ai --skill create-keyword-monitor
Clone the repo
git clone --depth 1 https://github.com/uptimerobot/ai

Made for: Claude Code.

Or install uptimerobot, the plugin that ships this one along with the rest of its 24 skills, 1 MCP server.

Wrote 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.

agentmods badge for create-keyword-monitor

README.md
[![agentmods](https://agentmods.dev/badge/skills/uptimerobot/ai/create-keyword-monitor/github.svg)](https://agentmods.dev/skills/uptimerobot/ai/create-keyword-monitor)
Your own site
<a href="https://agentmods.dev/skills/uptimerobot/ai/create-keyword-monitor"><img src="https://agentmods.dev/badge/skills/uptimerobot/ai/create-keyword-monitor/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.

agentmods 80×15 button for create-keyword-monitor

Your own site · 80×15
<a href="https://agentmods.dev/skills/uptimerobot/ai/create-keyword-monitor"><img src="https://agentmods.dev/badge/skills/uptimerobot/ai/create-keyword-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 733 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00032 $0.00733
Opus 5 $0.00016 $0.00367
Sonnet 5 $0.00006 $0.00147
Haiku 4.5 $0.00003 $0.00073

Measured 12d ago against content hash 8ca516577e82, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

create-keyword-monitor 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.

skills/create-keyword-monitor/SKILL.md · 74 lines

How it starts

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

Create a KEYWORD monitor

Preflight — read first. If you cannot see any uptimerobot:* MCP tools in your tool list, invoke the uptimerobot:setup skill 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.

Use when the user cares not just that an endpoint returns a 200, but that a specific string is present (login page has "Sign in") or absent (homepage is not showing "502 Bad Gateway"). For structured JSON assertions, prefer create-api-monitor instead.

Tool: create-monitor Required params: friendlyName, type: "KEYWORD", url (full URL), keywordValue, keywordType.

Minimal call

{
  "friendlyName": "Login page shows Sign in",
  "type": "KEYWORD",
  "url": "https://app.example.com/login",
  "keywordValue": "Sign in",
  "keywordType": "ALERT_NOT_EXISTS"
}

keywordType:

  • ALERT_NOT_EXISTS — alert when the keyword disappears (expected content missing → down).
  • ALERT_EXISTS — alert when the keyword appears (error string present → down).

Common optional params

All HTTP-monitor params are supported: httpMethodType, authType, httpUsername, httpPassword, followRedirections, checkSSLErrors, timeout, interval, sslExpirationReminder, domainExpirationReminder, responseTimeThreshold, assignedAlertContacts, tagNames, maintenanceWindowsIds.

KEYWORD-specific:

  • keywordCaseType0 for case-sensitive (default), 1 for case-insensitive.

Example: alert when a 500 message appears

{
  "friendlyName": "Homepage not erroring",
  "type": "KEYWORD",
  "url": "https://www.example.com/",
  "keywordValue": "Internal Server Error",
  "keywordType": "ALERT_EXISTS",
  "keywordCaseType": 1,
  "interval": 60,
  "assignedAlertContacts": [
    { "alertContactId": "10", "threshold": 0, "recurrence": 0 }
  ]
}

Common mistakes

  • Leaving off keywordType — it is required.
  • Using an HTTP monitor when the user said "alert me if the page shows X" — use KEYWORD.
  • Case-sensitivity confusion. Default is case-sensitive; pass keywordCaseType: 1 for insensitive.
  • keywordValue longer than 500 chars is rejected.
  • HEAD requests cannot match body content. If httpMethodType is HEAD, the keyword check will not work as expected.

Read the full file on GitHub · 74 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. 12d ago First seen · 74 lines · 32 tokens per session scan A 8ca516577e82

Subscribe to this mod's changes

create-keyword-monitor is a skill published in the GitHub repository uptimerobot/ai (24 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 733 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.

Related

Other skills, from other repositories

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…

ericrisco/rsc-harness · 88 tokens

create-test-run

Create a Kobiton test run from a test case or suite, then offer to monitor it. When the user gives only partial details (or just a test case id), fill the rest with sensible defaults that match the createTestRun schema, show a summary of what will run, and ask to proceed or customize before creating. After the run is…

kobiton/automate · 207 tokens

gatus-health

Automated health monitoring with Gatus.

bidewio/better-openclaw · 11 tokens

BytesAgain Monitor — Advanced Uptime & Performance Auditor

A website checker that measures whether sites respond, which HTTP status codes they return, and how long they take to respond. HTTP status codes are server replies such as 200 for success or 404 for a missing page.

bytesagain/ai-skills · 54 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/RuView · 27 tokens

sparc-methodology

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.

ruvnet/RuView · 29 tokens