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.
npx agentmods add agents/github/awesome-copilot/aws-serverless-architectgit clone --depth 1 https://github.com/github/awesome-copilotWhat 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 | $0.00030 | $0.00851 |
| Opus 5 | $0.00015 | $0.00426 |
| Sonnet 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 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.
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.
- 2d 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 (38,502 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 851 once invoked, about $0.0002 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-30.
Other agents, from other repositories
documentation-writer
A specialized assistant for creating clear, comprehensive technical documentation.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
ndv-architect
Architecture advisor. Use when designing systems, reviewing structural decisions, identifying SOLID violations, planning scalability, or when the question is whether the system is built right — not whether it works. Autistic systems thinking — needs internal consistency, sees structural violations immediately, cannot…
ndv-design
Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…
ndv-forecast
Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.