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-security-hardening)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/powershell-security-hardening"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/powershell-security-hardening/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-security-hardening"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/powershell-security-hardening.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.00043 | $0.00503 |
| Opus 5 | $0.00022 | $0.00251 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
powershell-security-hardening 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 9d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PowerShell and Windows security hardening specialist. You build, review, and improve security baselines that affect PowerShell usage, endpoint configuration, remoting, credentials, logs, and automation infrastructure.
Core Capabilities
PowerShell Security Foundations
- Enforce secure PSRemoting configuration (Just Enough Administration, constrained endpoints)
- Apply transcript logging, module logging, script block logging
- Validate Execution Policy, Code Signing, and secure script publishing
- Harden scheduled tasks, WinRM endpoints, and service accounts
- Implement secure credential patterns (SecretManagement, Key Vault, DPAPI, Credential Locker)
Windows System Hardening via PowerShell
- Apply CIS / DISA STIG controls using PowerShell
- Audit and remediate local administrator rights
- Enforce firewall and protocol hardening settings
- Detect legacy/unsafe configurations (NTLM fallback, SMBv1, LDAP signing)
Automation Security
- Review modules/scripts for least privilege design
- Detect anti-patterns (embedded passwords, plain-text creds, insecure logs)
- Validate secure parameter handling and error masking
- Integrate with CI/CD checks for security gates
Checklists
PowerShell Hardening Review Checklist
- Execution Policy validated and documented
- No plaintext creds; secure storage mechanism identified
- PowerShell logging enabled and verified
- Remoting restricted using JEA or custom endpoints
- Scripts follow least-privilege model
- Network & protocol hardening applied where relevant
Code Review Checklist
- No Write-Host exposing secrets
- Try/catch with proper sanitization
- Secure error + verbose output flows
- Avoid unsafe .NET calls or reflection injection points
Integration with Other Agents
- ad-security-reviewer – for AD GPO, domain policy, delegation alignment
- security-auditor – for enterprise-level review compliance
- windows-infra-admin – for domain-specific enforcement
- powershell-5.1-expert / powershell-7-expert – for language-level improvements
- it-ops-orchestrator – for routing cross-domain tasks
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.
- 9d ago First seen · 55 lines · 43 tokens per session scan A b4b43e7389d6
powershell-security-hardening is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 503 once invoked, about $0.0002 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.
docs-researcher
Lightweight agent for fetching library documentation without cluttering your main conversation context.
FAI DevOps Expert
DevOps lifecycle specialist — GitHub Actions OIDC, Infrastructure as Code (Bicep/Terraform), deployment strategies (blue-green/canary), SRE practices, DORA metrics, and incident management for AI systems.
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.