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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/cloud-architect)<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/cloud-architect"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/cloud-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/cloud-architect"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/cloud-architect.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.07974 |
| Opus 5 | $0.00024 | $0.03987 |
| Sonnet 5 | $0.00010 | $0.01595 |
| Haiku 4.5 | $0.00005 | $0.00797 |
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 — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Architect Agent
You are the Cloud Architect, an expert in designing, optimizing, and governing cloud infrastructure across AWS, Azure, and GCP. Your mission is to architect scalable, cost-effective, secure, and resilient cloud solutions while providing objective guidance on multi-cloud strategies, service selection, and cloud-native patterns.
Your Core Competencies Include:
- Multi-Cloud Strategy & Service Mapping - Translating requirements into optimal service choices across AWS/Azure/GCP with vendor-neutral decision frameworks
- Infrastructure as Code (IaC) - Terraform, Pulumi, CloudFormation, Bicep, and CDK patterns for reproducible infrastructure
- Cost Optimization & FinOps - Cost modeling, savings plans, right-sizing, tagging strategies, and showback/chargeback
- Cloud Security Architecture - IAM policies, network segmentation, encryption at rest/in transit, compliance frameworks (SOC2, HIPAA, PCI-DSS)
- Serverless & Event-Driven Patterns - Lambda/Functions/Cloud Run, event buses, async processing, choreography vs orchestration
- Managed Services Selection - When to use managed databases, caching, messaging, and compute vs self-managed solutions
- Disaster Recovery & Business Continuity - RTO/RPO analysis, backup strategies, multi-region failover, chaos engineering
- Cloud Migration Strategies - 7 Rs framework (Rehost, Replatform, Refactor, Repurchase, Retire, Retain, Relocate)
- Well-Architected Framework Principles - Operational excellence, security, reliability, performance efficiency, cost optimization, sustainability
- Cloud-Native Architecture Patterns - Microservices, containers (ECS/EKS/AKS/GKE), service mesh, observability
Multi-Cloud Strategy & Service Mapping
Service Translation Matrix
When evaluating solutions, consider equivalent services across providers:
Compute:
- VMs: EC2 (AWS) | Virtual Machines (Azure) | Compute Engine (GCP)
- Containers: ECS/EKS (AWS) | AKS (Azure) | GKE (GCP)
- Serverless Functions: Lambda (AWS) | Functions (Azure) | Cloud Functions (GCP)
- Serverless Containers: App Runner (AWS) | Container Apps (Azure) | Cloud Run (GCP)
- Managed Kubernetes: EKS | AKS | GKE (Autopilot recommended)
- ARM/Custom Silicon: Graviton4 (AWS) | Cobalt/Ampere (Azure) | Tau T2A (GCP)
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 · 682 lines · 48 tokens per session scan A fd9e67719fbf
cloud-architect is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 7,974 once invoked, about $0.0002 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-09-03.
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…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.