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/incident-triage)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/incident-triage"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/incident-triage/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/incident-triage"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/incident-triage.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.00006 | $0.00597 |
| Opus 5 | $0.00003 | $0.00298 |
| Sonnet 5 | $0.00001 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
incident-triage 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 6d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Better Stack Incident Triage
Triage current incidents across all monitored services. Lists unacknowledged incidents, groups by monitor, and identifies services requiring immediate attention. This is the primary daily workflow for MSP operations.
Prerequisites
- Better Stack MCP server connected with valid API token
- MCP tools
list_incidentsandget_incidentavailable
Steps
-
Fetch active incidents
Call
list_incidentsto retrieve incidents. Default to unresolved incidents (status=started). Iffromortodate filters are provided, include them. Paginate through all results up to the specifiedlimit. -
Categorize incidents
Group incidents by status: started (unacknowledged), acknowledged (in progress), resolved. Count incidents in each category.
-
Build triage summary table
For each incident, extract: incident ID, name/cause, started time, acknowledged time (if any), associated monitor, and notification status (call, SMS, email).
-
Highlight unacknowledged incidents
Flag incidents that have not been acknowledged -- these need immediate attention. Identify how long each has been open.
-
Provide next-step recommendations
Suggest acknowledging the most critical incidents first. For recurring incidents on the same monitor, recommend investigating the underlying cause. Cross-reference with logs using
/search-logs.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| status | string | No | started | Filter by status (started, acknowledged, resolved) |
| from | string | No | none | Start date filter (ISO 8601) |
| to | string | No | none | End date filter (ISO 8601) |
| limit | integer | No | 50 | Maximum number of incidents to return |
Examples
Triage All Active Incidents
/incident-triage
Show Acknowledged Incidents
/incident-triage --status acknowledged
Triage Incidents from Today
/incident-triage --from "2026-03-27"
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.
- 6d ago First seen · 78 lines · 6 tokens per session scan A 37ec0ef89ae3
incident-triage 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 6 tokens to every session and 597 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
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.