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/search-customers)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/search-customers"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/search-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/commands/wyre-ai/msp-claude-plugins/search-customers"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/search-customers.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.01698 |
| Opus 5 | $0.00005 | $0.00849 |
| Sonnet 5 | $0.00002 | $0.00340 |
| Haiku 4.5 | $0.00001 | $0.00170 |
Grade A, and why
search-customers scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X GET "https://app.atera.com/api/v3/customers" \ How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Atera Customers
Search for Atera customers by name, domain, or other attributes.
Prerequisites
- Valid Atera API key configured
- User must have customer read permissions
Steps
-
Search for customers
curl -s -X GET "https://app.atera.com/api/v3/customers" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Filter results by query match on customer name
- Apply limit parameter
-
Get contacts if requested For each matching customer:
curl -s -X GET "https://app.atera.com/api/v3/customers/{customer_id}/contacts" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json" -
Get agent summary if requested For each matching customer:
curl -s -X GET "https://app.atera.com/api/v3/agents?customerId={customer_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Count total agents
- Count online vs offline
-
Return customer list
- Customer ID and name
- Domain (if available)
- Contact count
- Agent summary (if requested)
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| query | string | Yes | - | Customer name or partial match |
| include_contacts | boolean | No | false | Include contact list |
| include_agents | boolean | No | false | Include agent count/summary |
| limit | integer | No | 25 | Maximum results |
Examples
Basic Search
/search-customers "Acme"
Include Contacts
/search-customers "Acme Corp" --include_contacts true
Include Agent Summary
/search-customers "Acme" --include_agents true
Full Details with Limit
/search-customers "Acme" --include_contacts true --include_agents true --limit 10
Search by Domain
/search-customers "acme.com"
Output
Basic Search Results
Customers Found: 3
| ID | Customer Name | Domain | Created |
|-------|------------------------|------------------|--------------------|
| 12345 | Acme Corporation | acme.com | 2023-01-15 |
| 12346 | Acme Industries | acme-ind.com | 2023-03-22 |
| 12347 | Acme LLC | acme-llc.com | 2024-06-01 |
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 · 273 lines · 9 tokens per session scan A 907e4d702671
search-customers 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 9 tokens to every session and 1,698 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.