tenant-exposure

tenant-exposure is a command for Claude Code from WYRE-AI/msp-claude-plugins. It costs 14 tokens per session (484 once invoked), scanned A, original, Apache-2.0.

A command that combines a customer's vulnerabilities, internet-facing weaknesses, leaked data, and scan history into a prioritized security report.

In plain words
What is it for?
Use it to prepare remediation plans, security reviews, or quarterly business review reports for a Blackpoint Cyber customer.
Why use it?
It gathers several security views in one place and highlights issues that need attention first, including stale or failed scans.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

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

Good fit Use it to prepare remediation plans, security reviews, or quarterly business review reports for a Blackpoint Cyber customer.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/wyre-ai/msp-claude-plugins/tenant-exposure
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.

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 tenant-exposure

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/tenant-exposure"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/tenant-exposure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 484 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.
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.00014 $0.00484
Opus 5 $0.00007 $0.00242
Sonnet 5 $0.00003 $0.00097
Haiku 4.5 $0.00001 $0.00048

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

Security

Grade A, and why

tenant-exposure 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.

msp-claude-plugins/blackpoint/blackpoint/commands/tenant-exposure.md · 74 lines

What it actually says

Blackpoint Tenant Exposure Report

Roll up a tenant's vulnerabilities, internet-facing exposures, dark-web leaks, and scan coverage into a QBR-ready, prioritized remediation report.

Prerequisites

  • Blackpoint MCP server connected with a valid BLACKPOINT_API_TOKEN
  • Tools: blackpoint_tenants_get, blackpoint_vulnerabilities_list, blackpoint_vulnerabilities_scans_list, blackpoint_vulnerabilities_external_list, blackpoint_vulnerabilities_darkweb_list

Steps

  1. Confirm the tenant

    Resolve tenant with blackpoint_tenants_get.

  2. Check scan freshness

    Call blackpoint_vulnerabilities_scans_list. If the last completed scan is stale or recent scans failed, lead the report with that caveat.

  3. Pull host vulnerabilities

    Call blackpoint_vulnerabilities_list for the tenant. Build the fix-now cohort: severity high/critical, status: open, exploit_available: true, patch_available: true.

  4. Pull external exposures

    Call blackpoint_vulnerabilities_external_list; group by exposure type (open port, vulnerable service, certificate, misconfig).

  5. Pull dark-web exposures

    Call blackpoint_vulnerabilities_darkweb_list. For credentials leaks, recommend forced password resets and an MFA check.

  6. Output

    Header (tenant, window, scan status), Fix-Now Vulnerabilities table, Other Open Findings counts, External Exposures table, Dark-Web Exposures table, and a numbered Remediation Priorities list.

Parameters

Parameter Type Required Default Description
tenant string Yes none Tenant name or ID

Examples

Exposure report for one tenant

/tenant-exposure "Acme Corp"
  • /partner-overview - Compare exposure across all tenants
  • /triage-detections - Pair exposure with active detections
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. 6d ago First seen · 74 lines · 14 tokens per session scan A 99ec5c4d6e01

Subscribe to this mod's changes

tenant-exposure 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 14 tokens to every session and 484 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.