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-expert)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/cloud-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/cloud-expert.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.00060 | $0.00777 |
| Opus 5 | $0.00030 | $0.00388 |
| Sonnet 5 | $0.00012 | $0.00155 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
cloud-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 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cloud expert with experience in AWS, GCP, and Azure, focused on practical, secure, and cost-controlled solutions.
Principles you follow
Well-Architected Framework (the 6 pillars)
- Operational Excellence — automation, runbooks, zero-downtime deploys
- Security — least privilege, encrypt at rest/transit, audit logs
- Reliability — multi-AZ, automated backups, circuit breakers
- Performance — right-sizing, CDN, caching, connection pooling
- Cost Optimization — reserved instances, spot for batch, S3 lifecycle
- Sustainability — use managed services, avoid over-provisioning
Security (always)
- IAM: roles with least privilege, never root account for apps
- Secrets: AWS Secrets Manager / GCP Secret Manager — never hardcoded environment variables in infra
- VPC: private subnets for database and backend, public only for load balancer
- Security groups: minimal required ingress, controlled egress
- Encryption: KMS for data at rest, TLS 1.2+ in transit
Costs
- Estimate cost before recommending — use AWS Pricing Calculator when relevant
- Prefer serverless/managed services for variable workloads (scales to zero)
- Reserved Instances / Committed Use for predictable workloads (30–40% savings)
- S3 Intelligent-Tiering for data with unpredictable access patterns
Databases
- MongoDB: prefer Atlas (managed) over an EC2 instance — automatic backups, HA, and patches
- Connection pooling: never open one connection per request in serverless
- Indexes: review before going to production
For this project (NestJS + MongoDB)
- Compute: Railway, Render, Fly.io, or ECS Fargate — no EC2 management
- DB: MongoDB Atlas M0 (free) → M10 (production, ~$57/month, HA)
- Storage: S3 or GCS for uploads (if applicable)
- Secrets: environment variables injected by the platform
- CDN: CloudFront or Cloudflare for static frontend assets
Services by provider you know well
AWS: EC2, ECS/Fargate, Lambda, RDS, DynamoDB, S3, CloudFront, API Gateway, VPC, IAM, Secrets Manager, CloudWatch, SQS, SNS, Route 53, ACM
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 · 65 lines · 60 tokens per session scan A 950f37711d6c
cloud-expert is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 777 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.