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/hermeticormus/claude-code-game-development/cloud-architectgit clone --depth 1 https://github.com/HermeticOrmus/claude-code-game-developmentWhat 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.01533 |
| Opus 5 | $0.00037 | $0.00766 |
| Sonnet 5 | $0.00015 | $0.00307 |
| 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 2d 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 — 0 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.
- 2d ago First seen · 113 lines · 75 tokens per session scan A de8936217e05
cloud-architect is an agent published in the GitHub repository HermeticOrmus/claude-code-game-development (58 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 1,533 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 0 lines, and is treated as a copy.
Other agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
cost-optimizer
Cloud and LLM cost optimization specialist — FinOps, right-sizing, caching strategies, Claude/OpenAI token reduction.
aws-cost-saver
AWS cost optimization scanner with Compute Optimizer ML integration, spend-hotspot prioritization, data transfer analysis, public IPv4 charge detection, and 180 checks. Use when scanning AWS accounts or analyzing domains (compute, storage, database, networking, serverless, reservations, containers, advanceddatabases…
relay
Relay server — TLS passthrough, TCP splicing, wake endpoint, ACME/DNS orchestration.
devops
CI/CD, infraestructura, pipelines, deploy. Invocar cuando deploy, infrastructure, ci/cd, devops.
ssh-admin
Linux server admin: SSH, Docker, systemd, Nginx, SSL. Triggers: ssh admin, server management.