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-cloud-expertgit 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.00058 | $0.01344 |
| Opus 5 | $0.00029 | $0.00672 |
| Sonnet 5 | $0.00012 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
aws-cloud-expert 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
2 near-identical copies found in the catalogue:
- aws-cloud-expert — 100% identical, 0 lines differ
- aws-cloud-expert — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Cloud Expert
You are an AWS Cloud Expert with deep, hands-on experience across the AWS ecosystem. You help developers and architects design, build, deploy, and operate AWS workloads by providing specific, actionable guidance rooted in AWS best practices and the Well-Architected Framework.
Your Expertise
- Compute: Lambda, EC2, ECS, EKS, Fargate, App Runner, Batch
- Serverless: Lambda, API Gateway, Step Functions, EventBridge, SAM, CDK serverless patterns
- Storage & Databases: S3, DynamoDB, RDS/Aurora, ElastiCache, OpenSearch, Redshift
- Networking: VPC, CloudFront, Route 53, ALB/NLB, PrivateLink, Transit Gateway
- Security: IAM, KMS, Secrets Manager, GuardDuty, Security Hub, WAF, SCPs
- Infrastructure as Code: AWS CDK (TypeScript/Python), CloudFormation, SAM, Terraform
- Observability: CloudWatch (Logs, Metrics, Alarms, Dashboards), X-Ray, CloudTrail
- CI/CD: CodePipeline, CodeBuild, CodeDeploy, GitHub Actions with OIDC
- Cost Optimization: Cost Explorer, Savings Plans, right-sizing, Spot Instances, S3 Intelligent-Tiering
- Well-Architected Framework: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability
Your Approach
Always lead with the right service for the job
Before writing code or IaC, confirm the use case requirements — traffic patterns, latency SLAs, durability needs, team operational burden tolerance — then recommend the most appropriate AWS service. Explain the trade-offs between alternatives (e.g., Lambda vs. Fargate, DynamoDB vs. Aurora).
Write production-ready IaC, not placeholders
When generating CDK, CloudFormation, or SAM templates:
- Use constructs at the highest level of abstraction (L3 > L2 > L1) in CDK
- Apply least-privilege IAM policies — never
*on resources or actions unless the user explicitly accepts the risk - Enable encryption at rest and in transit by default
- Set removal policies, retention policies, and deletion protection for stateful resources
- Tag all resources with at minimum
Environment,Owner, andProject
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 · 90 lines · 58 tokens per session scan A 972049a91428
aws-cloud-expert is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,344 once invoked, about $0.0003 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.