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 customersgit 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/customers)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/customers"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/customers/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/customers"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/customers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
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 →
- high Tool Misuse · line 56 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 156 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 221 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Data Exfiltration · line 93 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 170 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00034 | $0.02185 |
| Opus 5 | $0.00017 | $0.01092 |
| Sonnet 5 | $0.00007 | $0.00437 |
| Haiku 4.5 | $0.00003 | $0.00218 |
Grade B, and why
Alternative Payments Customers scanned grade B with 2 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 10d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const res = await fetch('https://public-api.alternativepayments.io/customers', { method: 'POST', Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://public-api.alternativepayments.io/customers?limit=100" \ How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alternative Payments Customers Management
Overview
Customers are the foundational entity in Alternative Payments — every invoice, payment request, transaction, and payout traces back to a customer. For MSPs, a customer is typically a managed services client (a business you bill on a recurring or project basis). Each customer can have one or more users — the individual contacts at that business who receive invoices and pay them.
This skill covers the read + safe-write customer surface: listing, retrieving, and creating customers, adding users, and archiving (a destructive operation). There is no direct money-movement operation here.
Anti-triggers
- The same client in the accounting ledger — an Alternative Payments
customer is a billing target on the payment rail with no GL contact record;
use
xero-contactsorqbo-customers. - The same client in the CRM — use
hubspot-companiesorsalesbuildr-companies-contacts. - Billing that customer — use
alternative-payments-invoicing.
Core Concepts
Customers and Users
| Entity | Description | MSP Example |
|---|---|---|
| Customer | A business you bill | "Acme Corp" |
| User | A contact at that business | "[email protected]" |
A customer is created first; users are then attached under
/customers/{id}/users. Invoices and payment requests reference the customer.
Customer Status
| Status | Description |
|---|---|
active |
Normal, billable customer (default) |
archived |
Hidden from default lists; preserved for history |
Archiving is performed with DELETE /customers/{id} — it does not hard-delete
the record. Treat it as destructive and confirm before running it.
Field Reference
Customer Fields
| Field | Type | Required | Description |
|---|---|---|---|
id |
string | System | Auto-generated unique identifier |
name |
string | Yes | Business/company name |
email |
string | No | Primary billing email |
phone |
string | No | Primary phone number |
external_id |
string | No | Your PSA/internal reference for cross-linking |
address |
object | No | Billing address (line1, city, region, postal_code, country) |
status |
string | Read-only | active or archived |
created_at |
datetime | Read-only | Creation timestamp |
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.
- 10d ago First seen · 263 lines · 34 tokens per session scan B 7277a03b59f9
Alternative Payments Customers 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 34 tokens to every session and 2,185 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cs-channel-message
A channel-message writing tool for search ads, advertising, customer relationship messages, and app notifications. It uses the NCM sequence—Need, Channel, Moment, Message, and CTA—to adapt wording to where and when customers see it.
commerce-detail-page-copy
A writing tool for Korean e-commerce product detail pages. It can generate a full 13-section page, assess an existing page, or create two persona-based copy sets.
commerce-ad-claim-compliance-kr
A pre-publication check for Korean advertising and product-page wording. It reviews claims against South Korea's advertising, food-safety, and e-commerce laws.
commerce-detail-page-planner
A strategy brief for deciding what a Korean e-commerce product page should say, show, and prioritise. It defines the main message, opening, page structure, sales channel approach, and photo checklist before copy, code, or images are made.
commerce-integrated-strategy
An e-commerce planning skill that combines customer research, product messaging, and store data into a one-page sales strategy with three priority actions.
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.