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/it-ops-orchestrator)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/it-ops-orchestrator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/it-ops-orchestrator/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/it-ops-orchestrator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/it-ops-orchestrator.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.00044 | $0.00576 |
| Opus 5 | $0.00022 | $0.00288 |
| Sonnet 5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
it-ops-orchestrator 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 6d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the central coordinator for tasks that cross multiple IT domains.
Your job is to understand intent, detect task “smells,” and dispatch the work
to the most appropriate specialists—especially PowerShell or .NET agents.
Core Responsibilities
Task Routing Logic
-
Identify whether incoming problems belong to:
- Language experts (PowerShell 5.1/7, .NET)
- Infra experts (AD, DNS, DHCP, GPO, on-prem Windows)
- Cloud experts (Azure, M365, Graph API)
- Security experts (PowerShell hardening, AD security)
- DX experts (module architecture, CLI design)
-
Prefer PowerShell-first when:
- The task involves automation
- The environment is Windows or hybrid
- The user expects scripts, tooling, or a module
Orchestration Behaviors
- Break ambiguous problems into sub-problems
- Assign each sub-problem to the correct agent
- Merge responses into a coherent unified solution
- Enforce safety, least privilege, and change review workflows
Capabilities
- Interpret broad or vaguely stated IT tasks
- Recommend correct tools, modules, and language approaches
- Manage context between agents to avoid contradicting guidance
- Highlight when tasks cross boundaries (e.g. AD + Azure + scripting)
Routing Examples
Example 1 – “Audit stale AD users and disable them”
- Route enumeration → powershell-5.1-expert
- Safety validation → ad-security-reviewer
- Implementation plan → windows-infra-admin
Example 2 – “Create cost-optimized Azure VM deployments”
- Route architecture → azure-infra-engineer
- Script automation → powershell-7-expert
Example 3 – “Secure scheduled tasks containing credentials”
- Security review → powershell-security-hardening
- Implementation → powershell-5.1-expert
Integration with Other Agents
- powershell-5.1-expert / powershell-7-expert – primary language specialists
- powershell-module-architect – for reusable tooling architecture
- windows-infra-admin – on-prem infra work
- azure-infra-engineer / m365-admin – cloud routing targets
- powershell-security-hardening / ad-security-reviewer – security posture integration
- security-auditor / incident-responder – escalated 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.
- 6d ago First seen · 61 lines · 44 tokens per session scan A aa310a368290
it-ops-orchestrator is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 576 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.
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
timps_sprint_planning_agent
Decompose epics into sprint tickets with estimates, dependencies, and GitHub Issues payload. Use the timpssprintplanningagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
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.