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 agentmods add commands/wyre-ai/msp-claude-plugins/run-powershellgit 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/run-powershell)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/run-powershell"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/run-powershell.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 | $0.00010 | $0.01862 |
| Opus 5 | $0.00005 | $0.00931 |
| Sonnet 5 | $0.00002 | $0.00372 |
| Haiku 4.5 | $0.00001 | $0.00186 |
Grade A, and why
run-powershell 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 5d 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/agents/{agent_id}" \ How it starts
The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run PowerShell on Atera Agent
Execute a PowerShell script on a specific Atera agent (endpoint) either inline or from the script library.
Prerequisites
- Valid Atera API key configured
- Agent must exist and be online
- User must have script execution permissions
- Either
scriptorscript_idmust be provided
Steps
-
Validate agent exists and is online
curl -s -X GET "https://app.atera.com/api/v3/agents/{agent_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Check agent exists
- Verify agent is online
- Capture device info for output
-
Get script content if using script_id
curl -s -X GET "https://app.atera.com/api/v3/customscripts/{script_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Validate script exists
- Show script name for confirmation
-
Execute the script
curl -s -X POST "https://app.atera.com/api/v3/agents/{agent_id}/runpowershell" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "Script": "<script_content>", "RunAs": "<run_as>", "Timeout": <timeout> }'- Capture execution ID for status polling
-
Poll for completion
curl -s -X GET "https://app.atera.com/api/v3/agents/{agent_id}/powershellstatus/{execution_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Poll every 5 seconds
- Respect timeout parameter
- Capture output when complete
-
Return execution results
- Execution status
- Script output (stdout)
- Error output (stderr)
- Execution duration
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| agent_id | integer | Yes | - | The agent ID to execute on |
| script | string | No* | - | Inline PowerShell script |
| script_id | integer | No* | - | Saved script ID from library |
| run_as | string | No | System | System or LoggedOnUser |
| timeout | integer | No | 300 | Timeout in seconds |
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.
- 5d ago First seen · 316 lines · 10 tokens per session scan A 03fe720b983d
run-powershell is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,862 once invoked, about $0.0001 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
research_codebase
Document codebase as-is with thoughts directory for historical context.
vibe-check
Audit a vibe-coded app across the six things that actually block shipping, and get a prioritized fix list.
iterate_plan
Iterate on existing implementation plans with thorough research and updates.
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
evaluate
Execute Evaluate stage to validate generated framework artifacts.
git
Git operations with intelligent commit messages and workflow optimization.