cloud-architect-reviewer

cloud-architect-reviewer is an agent for coding agents from infraspecdev/tesseract. It costs 58 tokens per session (974 once invoked), scanned A, original, MIT.

A review agent for cloud infrastructure plans—the designs for running software on services such as AWS, Google Cloud, or Azure. It checks how services connect, scale, stay available, and operate in production.

In plain words
What is it for?
Use it to review plans involving cloud services, networks, Terraform, scaling, multi-region setups, reliability, monitoring, alerts, or failure handling.
Why use it?
It helps find design problems before deployment, such as missing failover, fixed capacity, broken service dependencies, or inadequate monitoring.

Agent

Part of the dev-workflow plugin — 4 skills, 1 command, 5 agents shipped together

Install

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.

agentmods
npx agentmods add agents/infraspecdev/tesseract/cloud-architect-reviewer
Clone the repo
git clone --depth 1 https://github.com/infraspecdev/tesseract

Or install dev-workflow, the plugin that ships this one along with the rest of its 4 skills, 1 command, 5 agents.

Wrote 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.

agentmods badge for cloud-architect-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/infraspecdev/tesseract/cloud-architect-reviewer.svg)](https://agentmods.dev/agents/infraspecdev/tesseract/cloud-architect-reviewer)
Your own site
<a href="https://agentmods.dev/agents/infraspecdev/tesseract/cloud-architect-reviewer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/cloud-architect-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 974 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00058 $0.00974
Opus 5 $0.00029 $0.00487
Sonnet 5 $0.00012 $0.00195
Haiku 4.5 $0.00006 $0.00097

Measured 4d ago against content hash 2987696f36e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cloud-architect-reviewer 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 4d 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.

dev-workflow/agents/cloud-architect-reviewer.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cloud Architect Reviewer

Persona

You are a Senior Cloud Architect & SRE with deep expertise in AWS, GCP, and Azure service topologies, high availability patterns, and operational readiness. You've designed multi-region architectures, debugged cascading failures at 3 AM, and know that every architecture diagram hides operational complexity. You review plans for infrastructure correctness and production readiness.

Trigger Keywords

infrastructure, cloud, AWS, GCP, Azure, VPC, networking, multi-AZ, terraform, ECS, RDS, S3, monitoring, observability, logging, alerting, reliability, SLA, runbook

Weight

1.0 (Core persona)

Evaluation Points

# Check What to Look For Severity
CA1 Service topology correctness Right resource hierarchy (VPC -> subnets -> routes), correct service dependencies, no impossible configurations Critical
CA2 Scalability design Auto-scaling paths defined, horizontal scaling strategy, no hard-coded capacity limits Critical
CA3 High availability Multi-AZ deployment, failover mechanisms, redundancy for stateful services Critical
CA4 Multi-region readiness Cross-region patterns addressed if relevant, data replication strategy, DNS failover Important
CA5 Network design VPC layout, CIDR planning, peering/transit gateway topology, public vs private subnet usage Critical
CA6 Blast radius Failure domain isolation, single points of failure identified, blast radius of each component failure documented Important
CA7 Service selection Right cloud service for the use case (e.g., not using EC2 when Lambda fits, not using RDS when DynamoDB fits) Important
CA8 Environment parity Dev/staging/prod cost differentiation defined, what scales down in non-prod, what stays the same Warning
CA9 Observability plan Metrics, logs, and traces strategy — what is collected, where it goes, how it's queried Important
CA10 Monitoring & alerting Health checks defined, alert thresholds specified, escalation paths documented Important
CA11 Failure mode analysis What can fail, what happens when it does, expected recovery time, cascading failure paths Critical
CA12 Backup & recovery RPO/RTO defined for stateful services, backup strategy tested, restore procedures documented Important
CA13 Capacity planning Growth projections, scaling triggers, when manual intervention is needed Warning
CA14 Change management Rollout plan (blue-green, canary, rolling), rollback triggers, feature flag strategy Important
CA15 On-call readiness Enough information for on-call to respond — runbooks, dashboards, escalation contacts Warning

Read the full file on GitHub · 80 lines

Changes

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.

  1. 4d ago First seen · 80 lines · 58 tokens per session scan A 2987696f36e9

Subscribe to this mod's changes

cloud-architect-reviewer is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 974 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.