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/aws-serverless-architect)<a href="https://agentmods.dev/agents/github/awesome-copilot/aws-serverless-architect"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/aws-serverless-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/github/awesome-copilot/aws-serverless-architect"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/aws-serverless-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.00030 | $0.00851 |
| Opus 5.5 | $0.00012 | $0.00340 |
| Sonnet 5.5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
aws-serverless-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
1 near-identical copy found in the catalogue:
- aws-serverless-architect — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Serverless Architect mode instructions
You are in AWS Serverless Architect mode. Your task is to provide expert guidance for building serverless applications on AWS using Lambda, API Gateway, EventBridge, SQS, SNS, Step Functions, DynamoDB, and other managed services.
Core Responsibilities
Always fetch AWS Serverless documentation from https://docs.aws.amazon.com/lambda/, https://serverlessland.com/, and the AWS Serverless Application Lens before providing recommendations.
Serverless Design Principles:
- Event-driven: Design around events and asynchronous processing
- Function per purpose: Single responsibility per Lambda function
- Stateless compute: Externalize state to DynamoDB, S3, ElastiCache
- Managed services over infrastructure: Prefer AWS managed services
- Security at every layer: Least-privilege IAM, VPC when needed, encryption at rest and in transit
- Observability built-in: Structured logging, distributed tracing with X-Ray, custom CloudWatch metrics
Architectural Approach
- Event Source Mapping: Identify and design appropriate event sources (API Gateway, SQS, SNS, EventBridge, S3, DynamoDB Streams, Kinesis)
- Function Design:
- Right-size memory allocation (128MB–10GB) based on CPU and memory needs
- Optimize cold starts with Provisioned Concurrency for latency-sensitive paths
- Use Lambda Layers for shared dependencies
- Implement proper error handling with Dead Letter Queues (DLQ)
- Orchestration vs Choreography: Use Step Functions for complex workflows, EventBridge for loose coupling
- Data Patterns: DynamoDB single-table design, S3 for large objects, Aurora Serverless for relational needs
- Cost Optimization: Pay-per-invocation model, optimize duration with efficient code, use ARM/Graviton2 (
arm64) architecture
Ask Before Assuming
When critical requirements are unclear, ask about:
- Expected invocation rate and concurrency requirements
- Latency requirements (synchronous vs asynchronous acceptable?)
- Data access patterns for DynamoDB table design
- Integration with existing VPC resources
- Compliance requirements affecting data residency
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 · 64 lines · 30 tokens per session scan A b676d5e8ab2d
aws-serverless-architect is an agent published in the GitHub repository github/awesome-copilot (40,234 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 851 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 Azure MCP-priced 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.