Blackpoint Incident Response

Blackpoint Incident Response is a skill for Claude Code from WYRE-AI/msp-claude-plugins. It costs 64 tokens per session (1,276 once invoked), scanned A, original, Apache-2.0.

A guide for investigating Blackpoint Cyber detections by following the path from customer to asset to detection and related vulnerability.

In plain words
What is it for?
Use it for detection investigations, asset relationship mapping, and cross-checking alerts against vulnerabilities or other exposures.
Why use it?
It brings the relevant context together while making clear that the available tools only read information and do not change incident status.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Part of the blackpoint plugin — 4 skills, 5 commands, 3 agents shipped together

Good fit Use it for detection investigations, asset relationship mapping, and cross-checking alerts against vulnerabilities or other exposures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wyre-ai/msp-claude-plugins/incident-response
Install

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.

Any agent
npx skills add WYRE-AI/msp-claude-plugins --skill incident-response
Clone the repo
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-plugins

Made for: Claude Code.

Or install blackpoint, the plugin that ships this one along with the rest of its 4 skills, 5 commands, 3 agents.

Wrote 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.

agentmods badge for Blackpoint Incident Response

README.md
[![agentmods](https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/incident-response/github.svg)](https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/incident-response)
Your own site
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/incident-response"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/incident-response/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.

agentmods 80×15 button for Blackpoint Incident Response

Your own site · 80×15
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/incident-response"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,276 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.01276
Opus 5 $0.00032 $0.00638
Sonnet 5 $0.00013 $0.00255
Haiku 4.5 $0.00006 $0.00128

Measured 7d ago against content hash d9afdee8a99c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

Blackpoint Incident Response 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 7d 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.

msp-claude-plugins/blackpoint/blackpoint/skills/incident-response/SKILL.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blackpoint Incident Response

The functional Blackpoint tool surface today is read-only and centers on detections and the assets they fire against. This skill walks the investigation flow: tenant → asset → detections → vulnerabilities, plus dark-web and external-vulnerability cross-references.

Anti-triggers

  • Responding, acknowledging, isolating, or closing — despite the skill name there is no incident object and no write tool here. The MCP surface cannot mutate CompassOne state; response happens in the portal. If the intent is an actionable incident lifecycle, the operator is probably thinking of huntress-incidents or sentinelone-alerts.
  • blackpoint_alerts_* and blackpoint_tickets_* — those domains are stubs, not an alternative alerting surface. Detections are the only detection object Blackpoint exposes.
  • Exposure work in its own right — CVE filtering, scan history, dark-web, and external exposure have their own skill: blackpoint-vulnerability-management. Use this one only when a detection is the starting point.
  • Sweeping every customer rather than investigating one — use blackpoint-multi-tenant-operations.

API Tools

Tenants

Tool Purpose
blackpoint_tenants_list Partner's customer tenants
blackpoint_tenants_get Detail for one tenant

Assets

Tool Purpose
blackpoint_assets_list Assets for a tenant
blackpoint_assets_get Detail for one asset
blackpoint_assets_search Search assets by name / identifier
blackpoint_assets_relationships Asset relationships (parent / child / related)

Detections

Tool Purpose
blackpoint_detections_list Detections for the tenant / asset scope
blackpoint_detections_get Full detail for one detection

Vulnerabilities

Tool Purpose
blackpoint_vulnerabilities_list Known vulnerabilities for the scope
blackpoint_vulnerabilities_scans_list Recent scan results
blackpoint_vulnerabilities_darkweb_list Dark-web exposure findings
blackpoint_vulnerabilities_external_list External (internet-facing) vulnerabilities

Read the full file on GitHub · 142 lines

Changes

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.

  1. 7d ago First seen · 142 lines · 64 tokens per session scan A d9afdee8a99c

Subscribe to this mod's changes

Blackpoint Incident Response is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 8d ago), licensed Apache-2.0. It adds 64 tokens to every session and 1,276 once invoked, about $0.0003 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.