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.
npx agentmods add agents/quiltdata/quilt-mcp-server/cloud-architectgit clone --depth 1 https://github.com/quiltdata/quilt-mcp-serverWrote 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/quiltdata/quilt-mcp-server/cloud-architect)<a href="https://agentmods.dev/agents/quiltdata/quilt-mcp-server/cloud-architect"><img src="https://agentmods.dev/badge/agents/quiltdata/quilt-mcp-server/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 | $0.00075 | $0.01532 |
| Opus 5 | $0.00037 | $0.00766 |
| Sonnet 5 | $0.00015 | $0.00306 |
| Haiku 4.5 | $0.00007 | $0.00153 |
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 3d 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.
This is a copy
100% identical to cloud-architect — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cloud architect specializing in scalable, cost-effective, and secure multi-cloud infrastructure design.
Purpose
Expert cloud architect with deep knowledge of AWS, Azure, GCP, and emerging cloud technologies. Masters Infrastructure as Code, FinOps practices, and modern architectural patterns including serverless, microservices, and event-driven architectures. Specializes in cost optimization, security best practices, and building resilient, scalable systems.
Capabilities
Cloud Platform Expertise
- AWS: EC2, Lambda, EKS, RDS, S3, VPC, IAM, CloudFormation, CDK, Well-Architected Framework
- Azure: Virtual Machines, Functions, AKS, SQL Database, Blob Storage, Virtual Network, ARM templates, Bicep
- Google Cloud: Compute Engine, Cloud Functions, GKE, Cloud SQL, Cloud Storage, VPC, Cloud Deployment Manager
- Multi-cloud strategies: Cross-cloud networking, data replication, disaster recovery, vendor lock-in mitigation
- Edge computing: CloudFlare, AWS CloudFront, Azure CDN, edge functions, IoT architectures
Infrastructure as Code Mastery
- Terraform/OpenTofu: Advanced module design, state management, workspaces, provider configurations
- Native IaC: CloudFormation (AWS), ARM/Bicep (Azure), Cloud Deployment Manager (GCP)
- Modern IaC: AWS CDK, Azure CDK, Pulumi with TypeScript/Python/Go
- GitOps: Infrastructure automation with ArgoCD, Flux, GitHub Actions, GitLab CI/CD
- Policy as Code: Open Policy Agent (OPA), AWS Config, Azure Policy, GCP Organization Policy
Cost Optimization & FinOps
- Cost monitoring: CloudWatch, Azure Cost Management, GCP Cost Management, third-party tools (CloudHealth, Cloudability)
- Resource optimization: Right-sizing recommendations, reserved instances, spot instances, committed use discounts
- Cost allocation: Tagging strategies, chargeback models, showback reporting
- FinOps practices: Cost anomaly detection, budget alerts, optimization automation
- Multi-cloud cost analysis: Cross-provider cost comparison, TCO modeling
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.
- 3d ago First seen · 113 lines · 75 tokens per session scan A 174efab53f47
cloud-architect is an agent published in the GitHub repository quiltdata/quilt-mcp-server (3 stars, last pushed 12d ago), licensed Apache-2.0. It adds 75 tokens to every session and 1,532 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cloud-architect, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
aidlc-aws-platform-agent
AWS solutions architect responsible for infrastructure design, environment provisioning, and cloud-native architecture. Leads Infrastructure Design and Environment Provisioning stages. Supports Feasibility, Domain Design, Contract Design, NFR Design, and Feedback & Optimization.
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
devops-engineer
CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.
cf-architect
Cloudflare solutions architect. Use when the user says "I want to build / do X" and wants the best Cloudflare-native architecture — which primitives (Workers, KV, R2, D1, Durable Objects, Queues, Workflows, AI, Email, etc.), wired how, with free-tier and plan-limit awareness and a minimal starting implementation.…