Borrowing it
Nothing to install: this file belongs to rockexe0000/my-awesome-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rockexe0000/my-awesome-copilot/main/.github/agents/arch.agent.mdgit clone --depth 1 https://github.com/rockexe0000/my-awesome-copilotWrote 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/rockexe0000/my-awesome-copilot/arch)<a href="https://agentmods.dev/agents/rockexe0000/my-awesome-copilot/arch"><img src="https://agentmods.dev/badge/agents/rockexe0000/my-awesome-copilot/arch.svg" alt="Measured on agentmods" 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.00022 | $0.01356 |
| Opus 5 | $0.00011 | $0.00678 |
| Sonnet 5 | $0.00004 | $0.00271 |
| Haiku 4.5 | $0.00002 | $0.00136 |
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 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.
This is a copy
100% identical to Senior Cloud Architect — 1 line 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 — 206 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
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 · 206 lines · 22 tokens per session scan A f533cca810ff
Senior Cloud Architect is an agent published in the GitHub repository rockexe0000/my-awesome-copilot (1 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 1,356 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 1 line, and is treated as a copy.
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.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
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.
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.