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 vulnerability-managementgit 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/vulnerability-management)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/vulnerability-management"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/vulnerability-management/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/vulnerability-management"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/vulnerability-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 102 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00065 | $0.01158 |
| Opus 5 | $0.00032 | $0.00579 |
| Sonnet 5 | $0.00013 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
Blackpoint Vulnerability Management 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blackpoint Vulnerability Management
CompassOne exposes four exposure lenses against a tenant's assets: host-level vulnerabilities, scan history, dark-web leaks, and internet-facing external exposures. This skill covers all four and how to combine them into a prioritized remediation view.
Anti-triggers
- Patching, suppressing, or marking a finding fixed — the
statusvalues (fixed,ignored,false_positive) are filters on a read, not actions. Nothing here writes; remediation happens in the CompassOne portal or the patching tool. - Another vendor's vulnerability view —
sentinelone-vulnerabilitiesandsentinelone-misconfigurationscover different scanners with different CVE coverage. Do not merge severity counts across products. - Live threat activity — a vulnerability is a latent weakness;
something actually happening is a detection, in
blackpoint-incident-response. - Which host a CVE lands on — asset detail and topology are
blackpoint-asset-inventory.
API Tools
| Tool | Purpose |
|---|---|
blackpoint_vulnerabilities_list |
Host-level vulnerability findings |
blackpoint_vulnerabilities_scans_list |
Vulnerability scan history and status |
blackpoint_vulnerabilities_darkweb_list |
Dark-web exposures (leaked data) |
blackpoint_vulnerabilities_external_list |
Internet-facing external exposures |
Filters That Matter
blackpoint_vulnerabilities_list accepts:
tenant_id,asset_id— scopeseverity—low,medium,high,criticalstatus—open,fixed,ignored,false_positivecve_id— pivot on a specific CVEpatch_available— is a fix published?exploit_available— is it weaponized in the wild?
The fix-now cohort is the intersection: severity in
{high, critical}, status: open, exploit_available: true,
patch_available: true — a known, weaponized, fixable problem that
has not been fixed.
blackpoint_vulnerabilities_darkweb_list exposure types:
credentials, documents, data_breach, malware.
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 · 121 lines · 65 tokens per session scan A 7c8bb9b8be85
Blackpoint Vulnerability Management 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 65 tokens to every session and 1,158 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.
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.