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 commands/wyre-ai/msp-claude-plugins/monitor-statusgit clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/commands/wyre-ai/msp-claude-plugins/monitor-status)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/monitor-status"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/monitor-status.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.1 | $0.00009 | $0.00520 |
| Opus 5 | $0.00005 | $0.00260 |
| Sonnet 5 | $0.00002 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
monitor-status 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Better Stack Monitor Status
Check the current status of all uptime monitors, highlighting any that are down or in a degraded state. This is the primary dashboard check for MSP operations.
Prerequisites
- Better Stack MCP server connected with valid API token
- MCP tools
list_monitorsandget_monitoravailable
Steps
-
Fetch all monitors
Call
list_monitorsto retrieve all monitors. Ifstatusfilter is provided, filter results accordingly. Paginate through all results up to the specifiedlimit. -
Categorize by status
Group monitors by status: up, down, paused, pending, maintenance, validating. Count monitors in each category.
-
Build status summary table
For each monitor, extract: monitor ID, name, URL, status, last checked time, and check frequency.
-
Highlight downtime
Flag any monitors with status
downorvalidatingand identify which clients/services are affected. -
Provide next-step recommendations
For down monitors, suggest checking associated incidents with
/incident-triage. For paused monitors, verify they should still be paused.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| status | string | No | all | Filter by status (up, down, paused, pending, maintenance) |
| monitor_group | string | No | all | Filter by monitor group name |
| limit | integer | No | 100 | Maximum number of monitors to return |
Examples
Check All Monitors
/monitor-status
Show Only Down Monitors
/monitor-status --status down
Check Monitors for a Specific Client
/monitor-status --monitor_group "Acme Corp"
Error Handling
- Authentication Error: Verify
BETTERSTACK_API_TOKENis set correctly - Rate Limit: Wait and retry; use status filters to reduce result set
- No Results: Confirm filters are correct; no monitors may be configured yet
Related Commands
/create-monitor- Create a new uptime monitor/incident-triage- Triage incidents triggered by down monitors/status-page-update- Update status pages for affected services
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.
- 2d ago First seen · 77 lines · 9 tokens per session scan A 1ad4be1add69
monitor-status is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 3d ago), licensed Apache-2.0. It adds 9 tokens to every session and 520 once invoked, about $0.0000 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.
Other commands, from other repositories
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
speckit.git.initialize
Initialize a Git repository with an initial commit.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.