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/partner-overview)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/partner-overview"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/partner-overview.svg" alt="Measured on agentmods" 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.00018 | $0.00468 |
| Opus 5 | $0.00009 | $0.00234 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
partner-overview 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 3d 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
Blackpoint Partner Overview
A partner-level scorecard across every CompassOne tenant — detection volume and exposure posture rolled up so the MSP knows where to focus.
Prerequisites
- Blackpoint MCP server connected with a valid
BLACKPOINT_API_TOKEN - Tools:
blackpoint_tenants_list,blackpoint_detections_list,blackpoint_vulnerabilities_list,blackpoint_vulnerabilities_external_list,blackpoint_vulnerabilities_darkweb_list
Steps
-
Enumerate tenants
Call
blackpoint_tenants_listand page fully. -
Sweep detections per tenant
For each tenant,
blackpoint_detections_listover the look-back window,statusin {new,investigating}. Record count and severity distribution. -
Sweep exposure per tenant
For each tenant, pull
blackpoint_vulnerabilities_list,blackpoint_vulnerabilities_external_list, andblackpoint_vulnerabilities_darkweb_list. Record fix-now vulnerability count, external-exposure count, dark-web count. -
Build the portfolio scorecard
One row per tenant: detection count, critical/high count, fix-now vulns, external exposures, dark-web exposures. Compute an overall risk rank.
-
Output
A ranked portfolio table, a partner-wide summary line, and short notes on the highest-risk tenants. Flag any tenant with anomalous detection volume.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| hours | number | No | 24 | Detection look-back window |
Examples
Portfolio overview, last 24h
/partner-overview
Wider detection window
/partner-overview --hours 168
Related Commands
/triage-detections- Drill into the partner detection queue/tenant-exposure- Deep exposure report for one tenant
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.
- 3d ago First seen · 73 lines · 18 tokens per session scan A 9b76e55de717
partner-overview is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 18 tokens to every session and 468 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.