Better Stack Monitors

Better Stack Monitors is a skill for Claude Code from WYRE-AI/msp-claude-plugins. It costs 30 tokens per session (1,660 once invoked), scanned A, original, Apache-2.0.

A service-uptime monitoring system that periodically checks websites, network ports, or heartbeat signals. It can group, pause, and configure monitors with intervals, expected status codes, and alert thresholds.

In plain words
What is it for?
Use it to create and manage HTTP, TCP, and heartbeat checks, organize monitors, and configure their checking and alerting settings.
Why use it?
It detects downtime and performance problems before or as they affect users, while keeping the checks separate from alert routing and on-call schedules.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Part of the betterstack plugin — 5 skills, 4 commands, 2 agents shipped together

Good fit Use it to create and manage HTTP, TCP, and heartbeat checks, organize monitors, and configure their checking and alerting settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wyre-ai/msp-claude-plugins/monitors
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 WYRE-AI/msp-claude-plugins --skill monitors
Clone the repo
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-plugins

Made for: Claude Code.

Or install betterstack, the plugin that ships this one along with the rest of its 5 skills, 4 commands, 2 agents.

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 Better Stack Monitors

README.md
[![agentmods](https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/monitors/github.svg)](https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/monitors)
Your own site
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/monitors"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/monitors/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 Better Stack Monitors

Your own site · 80×15
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/monitors"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/monitors.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,660 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.00030 $0.01660
Opus 5 $0.00015 $0.00830
Sonnet 5 $0.00006 $0.00332
Haiku 4.5 $0.00003 $0.00166

Measured 5d ago against content hash 1b0910805332, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

Better Stack Monitors 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 5d 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.

msp-claude-plugins/betterstack/betterstack/skills/monitors/SKILL.md · 242 lines

How it starts

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

Better Stack Uptime Monitors

Overview

Uptime monitors are the core of Better Stack's monitoring platform. They periodically check URLs, ports, or heartbeats to detect downtime and performance degradation. Monitors can be grouped, paused, and configured with custom check intervals, expected status codes, and alerting thresholds.

Anti-triggers

  • An internal or RFC1918 target — checks run from Better Stack's public regions and cannot reach a private LAN. Reachability from inside the site is domotz-network, which polls from a collector on the LAN. Note it answers a different question: Domotz reports device and interface state, not synthetic HTTP/TCP probes, so there is no in-LAN equivalent of a Better Stack check.
  • Azure Monitor — same word, different product. Azure metrics, KQL, and alert rules are azure-mcp-observability.
  • Whether a piece of infrastructure is up — SNMP and ICMP polling of switches, firewalls, and APs is auvik-devices; a workstation or server under RMM is atera or ncentral.
  • Who gets woken when a check fails — the monitor holds the check; the routing and rotation are betterstack-oncall.

Key Concepts

Monitor Types

  • HTTP/HTTPS - Check a URL for expected status code and response
  • Ping (ICMP) - Ping a host to verify reachability
  • TCP - Check if a TCP port is open and responding
  • UDP - Check UDP port connectivity
  • Heartbeat - Expect periodic check-ins from cron jobs or services
  • DNS - Verify DNS record resolution
  • SMTP - Check mail server connectivity
  • POP3/IMAP - Check email retrieval services

Monitor Statuses

  • Up - Monitor is healthy, all checks passing
  • Down - Monitor detected downtime
  • Paused - Monitor is paused and not checking
  • Pending - Monitor was just created and hasn't checked yet
  • Maintenance - Monitor is in a maintenance window
  • Validating - Confirming downtime before alerting

Check Intervals

Better Stack supports check intervals from 30 seconds to 24 hours. Common intervals:

  • 30s - Critical production services
  • 60s - Standard web applications
  • 180s - Non-critical services
  • 300s - Background or internal services

Read the full file on GitHub · 242 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. 5d ago First seen · 242 lines · 30 tokens per session scan A 1b0910805332

Subscribe to this mod's changes

Better Stack Monitors is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,660 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-09-04.