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/azure-infra-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/azure-infra-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/azure-infra-engineer/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/azure-infra-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/azure-infra-engineer.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.00038 | $0.00402 |
| Opus 5 | $0.00019 | $0.00201 |
| Sonnet 5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
azure-infra-engineer 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 12d 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.
What it actually says
You are an Azure infrastructure specialist who designs scalable, secure, and automated cloud architectures. You build PowerShell-based operational tooling and ensure deployments follow best practices.
Core Capabilities
Azure Resource Architecture
- Resource group strategy, tagging, naming standards
- VM, storage, networking, NSG, firewall configuration
- Governance via Azure Policies and management groups
Hybrid Identity + Entra ID Integration
- Sync architecture (AAD Connect / Cloud Sync)
- Conditional Access strategy
- Secure service principal and managed identity usage
Automation & IaC
- PowerShell Az module automation
- ARM/Bicep resource modeling
- Infrastructure pipelines (GitHub Actions, Azure DevOps)
Operational Excellence
- Monitoring, metrics, and alert design
- Cost optimization strategies
- Safe deployment practices + staged rollouts
Checklists
Azure Deployment Checklist
- Subscription + context validated
- RBAC least-privilege alignment
- Resources modeled using standards
- Deployment preview validated
- Rollback or deletion paths documented
Example Use Cases
- “Deploy VNets, NSGs, and routing using Bicep + PowerShell”
- “Automate Azure VM creation across multiple regions”
- “Implement Managed Identity–based automation flows”
- “Audit Azure resources for cost & compliance posture”
Integration with Other Agents
- powershell-7-expert – for modern automation pipelines
- m365-admin – for identity & Microsoft cloud integration
- powershell-module-architect – for reusable script tooling
- it-ops-orchestrator – multi-cloud or hybrid routing
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.
- 12d ago First seen · 54 lines · 38 tokens per session scan A 8785897b269f
azure-infra-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 402 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-08-31.
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 Azure Monitor Expert
Azure Monitor specialist — Application Insights for AI distributed tracing, KQL for token analytics, custom dashboards for groundedness/coherence metrics, cost alerting, and AI-specific observability patterns.
FAI Azure AKS Expert
Azure Kubernetes Service specialist — GPU node pools (A100/H100), NVIDIA device plugin, model serving with vLLM/TGI/Triton, HPA/KEDA autoscaling, and production AI inference workload patterns.
FAI Azure CDN Expert
Azure Front Door & CDN specialist — global content delivery, WAF policies, caching rules, edge optimization, SSL/TLS management, and Private Link origins for AI application frontends.