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/triage-detections)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/triage-detections"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/triage-detections/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/triage-detections"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/triage-detections.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.00015 | $0.00518 |
| Opus 5 | $0.00008 | $0.00259 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
triage-detections 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.
What it actually says
Triage Blackpoint Detections
Sweep open CompassOne detections, rank them by severity and tenant impact, and produce a shift-ready priority list with dispositions.
Prerequisites
- Blackpoint MCP server connected with a valid
BLACKPOINT_API_TOKEN - Tools:
blackpoint_tenants_list,blackpoint_detections_list,blackpoint_detections_get,blackpoint_assets_get
Steps
-
Enumerate scope
If
tenantwas supplied, resolve it withblackpoint_tenants_list. Otherwise enumerate all tenants the partner can see. -
Sweep open detections
For each tenant, call
blackpoint_detections_listfiltered to the look-back window andstatusin {new,investigating}. -
Rank
Sort by
severity(critical → low), then tenant impact, then recency (newoutranks long-runninginvestigating). -
Enrich the top candidates
For the highest-ranked detections only, call
blackpoint_detections_getandblackpoint_assets_getto name the affected host. -
Assign dispositions
For each detection: escalate to Blackpoint SOC, investigate in-house, monitor, or likely-noise — with a one-line reason.
-
Output
A ranked priority table (tenant, detection ID, severity, type, asset, age, disposition) and a numbered recommended-actions list. Flag any tenant with anomalous detection volume.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| tenant | string | No | all tenants | Scope to one customer |
| hours | number | No | 24 | Look-back window in hours |
Examples
Triage the whole partner queue
/triage-detections
Triage one tenant over the last 8 hours
/triage-detections --tenant "Contoso" --hours 8
Related Commands
/investigate-detection- Drill into a single ranked detection/tenant-exposure- Pivot to a tenant's exposure posture
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 · 76 lines · 15 tokens per session scan A d5ccc1504562
triage-detections 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 15 tokens to every session and 518 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.