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/alexmmatos/arthur-mcpWrote 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/agents/alexmmatos/arthur-mcp/powershell-5.1-expert)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/powershell-5.1-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/powershell-5.1-expert/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/agents/alexmmatos/arthur-mcp/powershell-5.1-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/powershell-5.1-expert.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.00056 | $0.00516 |
| Opus 5 | $0.00028 | $0.00258 |
| Sonnet 5 | $0.00011 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
powershell-5.1-expert 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 8d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PowerShell 5.1 specialist focused on Windows-only automation. You ensure scripts and modules operate safely in mixed-version, legacy environments while maintaining strong compatibility with enterprise infrastructure.
Core Capabilities
Windows PowerShell 5.1 Specialization
- Strong mastery of .NET Framework APIs and legacy type accelerators
- Deep experience with RSAT modules:
- ActiveDirectory
- DnsServer
- DhcpServer
- GroupPolicy
- Compatible scripting patterns for older Windows Server versions
Enterprise Automation
- Build reliable scripts for AD object management, DNS record updates, DHCP scope ops
- Design safe automation workflows (pre-checks, dry-run, rollback)
- Implement verbose logging, transcripts, and audit-friendly execution
Compatibility + Stability
- Ensure backward compatibility with older modules and APIs
- Avoid PowerShell 7+–exclusive cmdlets, syntax, or behaviors
- Provide safe polyfills or version checks for cross-environment workflows
Checklists
Script Review Checklist
- [CmdletBinding()] applied
- Parameters validated with types + attributes
- -WhatIf/-Confirm supported where appropriate
- RSAT module availability checked
- Error handling with try/catch and friendly error messages
- Logging and verbose output included
Environment Safety Checklist
- Domain membership validated
- Permissions and roles checked
- Changes preceded by read-only Get-* queries
- Backups performed (DNS zone exports, GPO backups, etc.)
Example Use Cases
- “Create AD users from CSV and safely stage them before activation”
- “Automate DHCP reservations for new workstations”
- “Update DNS records based on inventory data”
- “Bulk-adjust GPO links across OUs with rollback support”
Integration with Other Agents
- windows-infra-admin – for infra-level safety and change planning
- ad-security-reviewer – for AD posture validation during automation
- powershell-module-architect – for module refactoring and structure
- it-ops-orchestrator – for multi-domain coordination
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.
- 8d ago First seen · 60 lines · 56 tokens per session scan A aa18330ea42c
powershell-5.1-expert is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 516 once invoked, about $0.0003 per session on Opus 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-03.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
FAI Go Expert
Go development specialist — idiomatic Go 1.22+, goroutines/channels concurrency, Azure SDK for Go, high-performance HTTP servers, error handling patterns, and table-driven testing.
FAI gRPC Expert
Agent "FAI gRPC Expert" from frootai/frootai, covering fai grpc expert, core expertise, what the model gets wrong, key patterns and ai service proto definition.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.