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 skills add WYRE-AI/msp-claude-plugins --skill oncallgit 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/skills/wyre-ai/msp-claude-plugins/oncall)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/oncall"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/oncall/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.
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/oncall"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/oncall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.01560 |
| Opus 5 | $0.00016 | $0.00780 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
Better Stack On-Call 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Better Stack On-Call Management
Overview
Better Stack Uptime includes integrated on-call scheduling that determines who gets paged when a monitor fails. Schedules define rotation patterns, and notification/escalation policies define how and when responders are alerted (via phone, SMS, email, or push). For MSPs, on-call is commonly configured per customer team, with separate schedules for each client's SLA requirements.
Anti-triggers
- Rotations that live in PagerDuty or Rootly — "who is on call",
"escalation policy", and "paging" are shared vocabulary across all
three products, and nothing in the phrasing disambiguates them. If
the MSP's paging system is not Better Stack, use
pagerduty-oncallorrootly-oncall. - Technician shifts, dispatch, or booked appointments — an on-call
rotation is not a service schedule; that lives in the PSA
(
autotask,halopsa,connectwise-psa). - Changing what a monitor checks rather than who it wakes — use
betterstack-monitors.
Key Concepts
Schedule Structure
Better Stack schedules define:
- Members - Responders in the rotation
- Rotation - Daily, weekly, or custom patterns
- Time zone - Critical for follow-the-sun setups
- Start date - When the rotation begins
Notification (Escalation) Policies
Policies define the alert cascade when a monitor goes down:
| Step | Description |
|---|---|
| 1 | Page the on-call schedule via phone, SMS, email, push |
| 2 (after timeout) | Escalate to a secondary schedule or individual |
| 3 (after timeout) | Escalate to team manager or broader group |
Better Stack calls these "notification policies" rather than "escalation policies", but they serve the same purpose.
Notification Methods
- Phone call - Voice call for critical alerts
- SMS - Text message notification
- Email - Email alert with incident details
- Push notification - Mobile app notification
- Slack/Teams - Integration-based notifications
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.
- 5d ago First seen · 192 lines · 33 tokens per session scan A 697613535295
Better Stack On-Call is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 7d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,560 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.
Other skills, from other repositories
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
content-card-news
A planning tool for four-card social media carousels on Instagram, Threads, and Kakao Channel, combining card copy, design guidance, image prompts, captions, and hashtags.
cs-voc-triage
A customer-feedback analysis tool that combines reviews and support contacts from multiple channels. VOC means “voice of the customer”: the comments, questions, complaints, and praise customers leave about a business.
design-copywriting
A copywriting workflow for marketing and product pages that uses a brand voice and returns structured text for page sections.
data-realestate
A lookup tool for reported South Korean property transactions using Ministry of Land data. It covers sales and rental deals for apartments, officetels, multi-family homes, houses, and commercial or office properties.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.