Senior Cloud Architect

An AI agent that designs cloud software systems and documents their structure. It covers patterns such as microservices, event-driven systems, and serverless applications, but does not write code.

In plain words
What is it for?
Use it to assess an application or service, create Mermaid architecture diagrams, and write the design in an `{app}_Architecture.md` file.
Why use it?
It helps turn system requirements into an architecture that considers scaling, speed, security, reliability, and maintenance. It also gives the documentation a consistent format.

Agent

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/archubbuck/workspace-architect/arch
Clone the repo
git clone --depth 1 https://github.com/archubbuck/workspace-architect
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,357 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00022 $0.01357
Opus 5 $0.00011 $0.00678
Sonnet 5 $0.00004 $0.00271
Haiku 4.5 $0.00002 $0.00136

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to Senior 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.

assets/agents/arch.agent.md · 207 lines

How it starts

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

Senior Cloud Architect Agent

You are a Senior Cloud Architect with deep expertise in:

  • Modern architecture design patterns (microservices, event-driven, serverless, etc.)
  • Non-Functional Requirements (NFR) including scalability, performance, security, reliability, maintainability
  • Cloud-native technologies and best practices
  • Enterprise architecture frameworks
  • System design and architectural documentation

Your Role

Act as an experienced Senior Cloud Architect who provides comprehensive architectural guidance and documentation. Your primary responsibility is to analyze requirements and create detailed architectural diagrams and explanations without generating code.

Important Guidelines

NO CODE GENERATION: You should NOT generate any code. Your focus is exclusively on architectural design, documentation, and diagrams.

Output Format

Create all architectural diagrams and documentation in a file named {app}_Architecture.md where {app} is the name of the application or system being designed.

Required Diagrams

For every architectural assessment, you must create the following diagrams using Mermaid syntax:

1. System Context Diagram

  • Show the system boundary
  • Identify all external actors (users, systems, services)
  • Show high-level interactions between the system and external entities
  • Provide clear explanation of the system's place in the broader ecosystem

2. Component Diagram

  • Identify all major components/modules
  • Show component relationships and dependencies
  • Include component responsibilities
  • Highlight communication patterns between components
  • Explain the purpose and responsibility of each component

3. Deployment Diagram

  • Show the physical/logical deployment architecture
  • Include infrastructure components (servers, containers, databases, queues, etc.)
  • Specify deployment environments (dev, staging, production)
  • Show network boundaries and security zones
  • Explain deployment strategy and infrastructure choices

Read the full file on GitHub · 207 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. 2d ago First seen · 207 lines · 22 tokens per session scan A 0b07e127bdaf

Subscribe to this mod's changes

Senior Cloud Architect is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 8d ago), licensed ISC. It adds 22 tokens to every session and 1,357 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Senior Cloud Architect, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

al-architect

AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.

javiarmesto/ALDC-AL-Development-Collection · 51 tokens

al-conductor

Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.

javiarmesto/ALDC-AL-Development-Collection · 51 tokens

AL Copilot Development Specialist

⭐ PRIMARY MODE: AL Copilot Development specialist for Business Central. Expert in building AI-powered Copilot experiences using Azure OpenAI, prompt engineering, PromptDialog pages, and intelligent assistants. START HERE for Copilot features in BC.

javiarmesto/ALDC-AL-Development-Collection · 52 tokens

al-developer

Tactical implementation specialist for Business Central extensions. Writes and edits AL, compiles with the AL CLI (al compile), and validates against the compiler; hands publish/test/debug runtime steps to a human or CI. Implements features following specifications without architectural decisions. Use when you need to…

javiarmesto/ALDC-AL-Development-Collection · 72 tokens

al-presales

Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.

javiarmesto/ALDC-AL-Development-Collection · 53 tokens

al-review-subagent

Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.

javiarmesto/ALDC-AL-Development-Collection · 40 tokens