Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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/github/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/github/awesome-copilot/arch)<a href="https://agentmods.dev/agents/github/awesome-copilot/arch"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/arch/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/github/awesome-copilot/arch"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/arch.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.00022 | $0.01357 |
| Opus 5.5 | $0.00009 | $0.00543 |
| Sonnet 5.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 1mo 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- Senior Cloud Architect — 100% identical, 1 lines differ
- Senior Cloud Architect — 100% identical, 0 lines differ
- Senior Cloud Architect — 100% identical, 0 lines differ
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
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.
- 1mo ago First seen · 207 lines · 22 tokens per session scan A 0b07e127bdaf
Senior Cloud Architect is an agent published in the GitHub repository github/awesome-copilot (40,052 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,357 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
software-engineer
SWE role definition for /implement-universal. Loaded by the orchestrator at the start of the SWE phase. Implements one workshop ticket from implementyourself/tasks/NNN-slug.groomed.md, populates the skeleton under implementyourself/src/, runs make QA + the ticket's e2e target, and produces a hand-off message in the…
03-Architect
Expert Architect providing guidance using Azure Well-Architected Framework principles and Microsoft best practices. Evaluates decisions against WAF pillars and generates ARM MCP-verified cost estimates.
04g-Governance
Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.
ndv-signal
Metrics skeptic. Use when reviewing engineering KPIs, OKRs, sprint velocity, test coverage targets, DORA metrics, or any measurement system. Audits whether metrics measure what they claim to measure. Goodhart's Law as a cognitive style — the moment a measure becomes a target, it stops being a measure, and Signal…
aws-architect
Strategic guidance for AWS service selection, cost optimization, and security best practices. Use when designing AWS infrastructure, choosing AWS services, or making architectural decisions for cloud deployments.
ndv-honest
Pure communication layer. Direct, ruthless, zero filler. Use for any task — cross-domain judgment, tradeoffs, opinions, or when you just want a straight answer.