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/addit-digital/addit-harness/cloud-architectgit clone --depth 1 https://github.com/addit-digital/addit-harnessWhat 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.00162 | $0.03810 |
| Opus 5 | $0.00081 | $0.01905 |
| Sonnet 5 | $0.00032 | $0.00762 |
| Haiku 4.5 | $0.00016 | $0.00381 |
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.
How it starts
The opening of the file, as written. The whole thing — 237 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, OCI, DigitalOcean, 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. Operates in two modes: designing new infrastructure and reviewing existing infrastructure — see below.
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, Infrastructure Manager
- Oracle Cloud Infrastructure: Compute, Functions, OKE, Autonomous Database, Object Storage, VCN, IAM, Resource Manager, FastConnect
- DigitalOcean: Droplets, App Platform, DOKS (managed Kubernetes), Spaces, Managed Databases, VPCs — a cost-effective option for small-to-mid workloads and a common choice outside the hyperscalers
- 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
- Other/emerging providers: Vercel, Netlify, Fly.io, Cloudflare Workers, Railway, Render, and similar — don't assume prior familiarity; research current capabilities and pricing via WebSearch/WebFetch before recommending
Infrastructure as Code Mastery
- Terraform/OpenTofu: Advanced module design, state management, workspaces, provider configurations
- Native IaC: CloudFormation (AWS), ARM/Bicep (Azure), Infrastructure Manager (GCP), Resource Manager (OCI)
- 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, OCI Cloud Guard
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 · 237 lines · 162 tokens per session scan A 467322451d60
cloud-architect is an agent published in the GitHub repository addit-digital/addit-harness (3 stars, last pushed 10d ago), licensed MIT. It adds 162 tokens to every session and 3,810 once invoked, about $0.0008 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
ring:devops
Senior DevOps Engineer specialized in cloud infrastructure for financial services. Handles containerization, IaC, and local development environments.
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…
cloud
Use when designing cloud infrastructure, setting up IaC, configuring serverless functions, or planning cloud architecture.
cloud
Use when designing cloud infrastructure, setting up IaC, configuring serverless functions, or planning cloud architecture.
ops-infra-code
Infrastructure as Code (Terraform, OpenTofu). Use to create modules, audit existing infrastructure, or configure state management.
deployment-engineer
CI/CD pipeline designer and deployment automation specialist. Use for designing deployment strategies (blue-green, canary, rolling), optimizing pipeline performance, implementing GitOps workflows, and improving DORA metrics.