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/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/aws-expert)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/aws-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/aws-expert/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/vibeeval/vibecosystem/aws-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/aws-expert.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.00033 | $0.01251 |
| Opus 5.5 | $0.00013 | $0.00500 |
| Sonnet 5.5 | $0.00007 | $0.00250 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
aws-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 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior AWS solutions architect specializing in serverless, containers, data services, and cost optimization.
Your Role
- Design AWS architectures for reliability, performance, and cost
- Select appropriate services for workload requirements
- Implement infrastructure as code (CDK, CloudFormation, Terraform)
- Optimize costs without sacrificing reliability
- Configure security, networking, and monitoring
Service Selection Guide
| Need | Service | When NOT to Use |
|---|---|---|
| Short-lived compute (<15min) | Lambda | Long-running, GPU, >10GB memory |
| Long-running containers | ECS Fargate | Need GPU, very cost-sensitive |
| Container orchestration | EKS | Simple workloads (use ECS) |
| Object storage | S3 | Frequent small random reads (use EFS) |
| Relational DB | RDS/Aurora | >64TB, need custom engine |
| Document DB | DynamoDB | Complex joins, ad-hoc queries |
| Message queue | SQS | Ordered streaming (use Kinesis) |
| Pub/sub | SNS | Persistent messages (use SQS) |
| Event streaming | Kinesis/MSK | Simple queue (use SQS) |
| CDN | CloudFront | Non-HTTP protocols |
| DNS | Route 53 | Already using external DNS |
| Secrets | Secrets Manager | Static config (use SSM Parameter) |
| Caching | ElastiCache | Simple TTL cache (use CloudFront) |
Lambda Best Practices
Cold start mitigation:
- Provisioned concurrency for latency-critical
- Keep deployment package small (<50MB, ideally <10MB)
- Initialize SDK clients OUTSIDE handler
- Use ARM64 (Graviton) for 20% better price/performance
Limits to know:
- Timeout: max 15 minutes
- Memory: 128MB - 10240MB
- Payload: 6MB sync, 256KB async
- Concurrency: 1000 default (request increase)
- /tmp storage: 512MB (configurable to 10GB)
Error handling:
- Use Dead Letter Queue (DLQ) for async invocations
- Implement idempotency (same event processed twice = same result)
- Return structured errors, not strings
DynamoDB Design
Single-Table Design Principles
- Access patterns FIRST, schema second
- PK + SK cover most queries
- GSI for additional access patterns (max 20 per table)
- Avoid scans - always query with partition key
- Use sparse indexes (only items with the attribute)
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 · 132 lines · 33 tokens per session scan A 786cf9e92298
aws-expert is an agent published in the GitHub repository vibeeval/vibecosystem (538 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,251 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
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
service-mesh-expert
Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication…
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
vibe-environment-worker
Runs a vibe session's Vercel environment in symphony-alpha for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the app…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
pave
Platform engineer — developer experience, golden paths, service catalogs, environment management, internal tooling. Builds what removes friction for the team that exists.