run-script

run-script is a command for Claude Code from WYRE-AI/msp-claude-plugins. It costs 11 tokens per session (1,939 once invoked), scanned A, original, Apache-2.0.

A command that runs a stored ConnectWise Automate script on a managed endpoint, such as a PowerShell, batch, VBScript, or native Automate routine. It can check the computer and script before execution and optionally wait for the result.

In plain words
What is it for?
Use it to target a computer by ID or hostname, pass script parameters, execute the routine, and retrieve its completion status or result.
Why use it?
It avoids manually finding the device, checking whether it is online, validating parameters, and dispatching the script through the management system.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the connectwise-automate plugin — 2 skills, 2 commands, 1 agent shipped together

Good fit Use it to target a computer by ID or hostname, pass script parameters, execute the routine, and retrieve its completion status or result.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/wyre-ai/msp-claude-plugins/run-script
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 connectwise-automate, the plugin that ships this one along with the rest of its 2 skills, 2 commands, 1 agent.

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 run-script

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/run-script"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/run-script.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,939 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.00011 $0.01939
Opus 5.5 $0.00004 $0.00776
Sonnet 5.5 $0.00002 $0.00388
Haiku 4.5 $0.00001 $0.00194

Measured 1mo ago against content hash b50c640bafb7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

run-script 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.

msp-claude-plugins/connectwise/automate/commands/run-script.md · 348 lines

How it starts

The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run Script

Execute a script on an endpoint in ConnectWise Automate with optional parameters.

Prerequisites

  • Valid ConnectWise Automate API credentials configured
  • CONNECTWISE_AUTOMATE_SERVER environment variable set
  • CONNECTWISE_AUTOMATE_USERNAME and CONNECTWISE_AUTOMATE_PASSWORD environment variables set
  • Computer must be online for immediate script execution

Steps

  1. Resolve computer identifier

    • If numeric, use as Computer ID directly
    • Otherwise, search by hostname
  2. Verify computer is online

    • Check computer status
    • If offline, return error with last contact time
  3. Resolve script

    • If numeric, use as Script ID directly
    • Otherwise, search scripts by name
  4. Validate script parameters

    • Get script definition to check required parameters
    • Verify all required parameters are provided
    • Parse params string into key-value pairs
  5. Execute script

    POST /cwa/api/v1/Computers/{computerID}/Scripts/{scriptID}/Execute
    Authorization: Bearer {token}
    Content-Type: application/json
    
    {
      "Parameters": {
        "key1": "value1",
        "key2": "value2"
      }
    }
    
  6. Handle result

    • If --wait flag, poll for completion
    • Return execution status and output

Parameters

Parameter Type Required Default Description
computer string Yes - Computer hostname or ID
script string Yes - Script name or ID
params string No - Parameters as key=value,key2=value2
wait flag No false Wait for script completion

Examples

Basic Script Execution

/run-script "ACME-DC01" "Clear Temp Files"

With Parameters

/run-script "ACME-DC01" "Clear Temp Files" --params "days=30,path=C:\\Temp"

Wait for Completion

/run-script "ACME-DC01" "Clear Temp Files" --wait

Using Computer ID

/run-script 12345 "Clear Temp Files" --wait

Read the full file on GitHub · 348 lines

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. 1mo ago First seen · 348 lines · 11 tokens per session scan A b50c640bafb7

Subscribe to this mod's changes

run-script is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 1,939 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.