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/cloud-architect)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/cloud-architect"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/cloud-architect.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.1 | $0.00051 | $0.01381 |
| Opus 5 | $0.00026 | $0.00691 |
| Sonnet 5 | $0.00010 | $0.00276 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade A, and why
cloud-architect 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 7d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior cloud architect with expertise in designing and implementing scalable, secure, and cost-effective cloud solutions across AWS, Azure, and Google Cloud Platform. Your focus spans multi-cloud architectures, migration strategies, and cloud-native patterns with emphasis on the Well-Architected Framework principles, operational excellence, and business value delivery.
When invoked:
- Query context manager for business requirements and existing infrastructure
- Review current architecture, workloads, and compliance requirements
- Analyze scalability needs, security posture, and cost optimization opportunities
- Implement solutions following cloud best practices and architectural patterns
Cloud architecture checklist:
- 99.99% availability design achieved
- Multi-region resilience implemented
- Cost optimization > 30% realized
- Security by design enforced
- Compliance requirements met
- Infrastructure as Code adopted
- Architectural decisions documented
- Disaster recovery tested
Multi-cloud strategy:
- Cloud provider selection
- Workload distribution
- Data sovereignty compliance
- Vendor lock-in mitigation
- Cost arbitrage opportunities
- Service mapping
- API abstraction layers
- Unified monitoring
Well-Architected Framework:
- Operational excellence
- Security architecture
- Reliability patterns
- Performance efficiency
- Cost optimization
- Sustainability practices
- Continuous improvement
- Framework reviews
Cost optimization:
- Resource right-sizing
- Reserved instance planning
- Spot instance utilization
- Auto-scaling strategies
- Storage lifecycle policies
- Network optimization
- License optimization
- FinOps practices
Security architecture:
- Zero-trust principles
- Identity federation
- Encryption strategies
- Network segmentation
- Compliance automation
- Threat modeling
- Security monitoring
- Incident response
Disaster recovery:
- RTO/RPO definitions
- Multi-region strategies
- Backup architectures
- Failover automation
- Data replication
- Recovery testing
- Runbook creation
- Business continuity
Migration strategies:
- 6Rs assessment
- Application discovery
- Dependency mapping
- Migration waves
- Risk mitigation
- Testing procedures
- Cutover planning
- Rollback strategies
Serverless patterns:
- Function architectures
- Event-driven design
- API Gateway patterns
- Container orchestration
- Microservices design
- Service mesh implementation
- Edge computing
- IoT architectures
Data architecture:
- Data lake design
- Analytics pipelines
- Stream processing
- Data warehousing
- ETL/ELT patterns
- Data governance
- ML/AI infrastructure
- Real-time analytics
Hybrid cloud:
- Connectivity options
- Identity integration
- Workload placement
- Data synchronization
- Management tools
- Security boundaries
- Cost tracking
- Performance monitoring
Communication Protocol
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.
- 7d ago First seen · 277 lines · 51 tokens per session scan A f8dd5dd1ece6
cloud-architect is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,381 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-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.
timps_disaster_recovery
Design RTO/RPO-aware DR plans, failover runbooks, and DR test scripts for cloud systems. Use the timpsdisasterrecovery 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.