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/list-computers)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/list-computers"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/list-computers/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/list-computers"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/list-computers.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.00010 | $0.01866 |
| Opus 5.5 | $0.00004 | $0.00746 |
| Sonnet 5.5 | $0.00002 | $0.00373 |
| Haiku 4.5 | $0.00001 | $0.00187 |
Grade A, and why
list-computers 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 1mo 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List Computers
List computers in ConnectWise Automate with optional filters for client, location, status, and OS type.
Prerequisites
- Valid ConnectWise Automate API credentials configured
CONNECTWISE_AUTOMATE_SERVERenvironment variable setCONNECTWISE_AUTOMATE_USERNAMEandCONNECTWISE_AUTOMATE_PASSWORDenvironment variables set
Steps
-
Build filter condition
- Start with empty condition
- Add client filter if specified
- Add location filter if specified
- Add status filter if specified
- Add OS filter if specified
-
Construct API request
GET /cwa/api/v1/Computers?condition={encoded_condition}&pageSize={limit} Authorization: Bearer {token} -
Build filter examples
// Client filter if (client) { conditions.push(`Client.Name contains '${client}'`); } // Status filter if (status === 'online') { conditions.push("Status = 'Online'"); } else if (status === 'offline') { conditions.push("Status = 'Offline'"); } // OS filter if (os === 'server') { conditions.push("OS contains 'Server'"); } else if (os === 'workstation') { conditions.push("OS contains 'Windows' and not (OS contains 'Server')"); } const condition = conditions.join(' and '); -
Execute request with pagination
- Use pageSize from limit or default 50
- Handle pagination if more results exist
-
Format and return results
- Computer name
- Client name
- Location
- Status
- IP address
- OS
- Last contact
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| client | string | No | - | Filter by client name (partial match) |
| location | string | No | - | Filter by location name (partial match) |
| status | string | No | - | Filter: online, offline |
| os | string | No | - | Filter: windows, server, workstation, macos, linux |
| limit | number | No | 50 | Max results to return (max 500) |
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.
- 1mo ago First seen · 285 lines · 10 tokens per session scan A b467838ea702
list-computers is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 1,866 once invoked, about $0.0000 per session on Opus 5.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
vibe-check
Audit a vibe-coded app across the six things that actually block shipping, and get a prioritized fix list.
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.