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.
git 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/status-page-update)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/status-page-update"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/status-page-update/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/commands/wyre-ai/msp-claude-plugins/status-page-update"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/status-page-update.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00676 |
| Opus 5 | $0.00005 | $0.00338 |
| Sonnet 5 | $0.00002 | $0.00135 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
status-page-update 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Better Stack Status Page Update
Review and update status pages with current service status, post incident updates, or schedule maintenance notifications. Used for client-facing communication during outages and planned maintenance.
Prerequisites
- Better Stack MCP server connected with valid API token
- MCP tools
list_status_pages,get_status_page,list_status_page_sections, andcreate_status_page_incidentavailable
Steps
-
Identify target status page
If
status_page_idis provided, fetch that page. Otherwise, calllist_status_pagesto show all available pages and let the user select one. -
Review current status
Call
get_status_pageto see the current page configuration. Calllist_status_page_sectionsto see all resources/components and their current statuses. -
Execute the requested action
Based on the
actionparameter:- review - Display the current status of all components. Highlight any that are not operational.
- post-incident - Use
create_status_page_incidentto post an incident update with the providedmessage. - post-maintenance - Use
create_status_page_incidentto post a planned maintenance notice with the providedmessage.
-
Verify update
After posting an update, confirm it was published successfully and report the update details.
-
Recommend follow-up
Suggest updating the status page when the incident is resolved, or remind about resuming monitors after maintenance.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| status_page_id | string | No | prompt | Status page ID (will list pages if not provided) |
| action | string | No | review | Action: review, post-incident, post-maintenance |
| message | string | No | none | Status update message for posts |
Examples
Review Status Page
/status-page-update
Review a Specific Status Page
/status-page-update --status_page_id "sp-123"
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 · 86 lines · 11 tokens per session scan A db5a1d30fe1a
status-page-update is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 7d ago), licensed Apache-2.0. It adds 11 tokens to every session and 676 once invoked, about $0.0001 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.