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 skills/caiaffa/claude-code-ultimate-engineering-system/aws-production-systemsnpx skills add caiaffa/claude-code-ultimate-engineering-system --skill aws-production-systemsgit clone --depth 1 https://github.com/caiaffa/claude-code-ultimate-engineering-systemWrote 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/skills/caiaffa/claude-code-ultimate-engineering-system/aws-production-systems)<a href="https://agentmods.dev/skills/caiaffa/claude-code-ultimate-engineering-system/aws-production-systems"><img src="https://agentmods.dev/badge/skills/caiaffa/claude-code-ultimate-engineering-system/aws-production-systems.svg" alt="Measured on agentmods" 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.00027 | $0.00616 |
| Opus 5 | $0.00014 | $0.00308 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
aws-production-systems 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 6d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Ensure AWS architectures are safe to run, understandable to operate, and justifiable in cost and complexity.
When to use
- Designing or reviewing AWS-native systems.
- Choosing managed services.
- Reviewing IAM, queues, storage, networking, or secrets.
- Planning resilience or disaster recovery.
Handoff
- Receives from: principal-engineer (architecture decision) or backend-platform-engineer (infra needs).
- Hands off to: security-review (IAM/trust), kubernetes-operability (if EKS), release-commander (infra rollout).
Before answering
Identify: workload type, traffic pattern, availability requirements, cost sensitivity, team ability to operate the chosen services, network and security constraints.
Service selection principles
| Need | Prefer | Avoid unless justified |
|---|---|---|
| Async jobs | SQS + Lambda or ECS | Step Functions for simple pipelines |
| API backend | ECS/Fargate or EKS | Lambda if > 15s or stateful |
| Storage | S3 (objects), RDS (relational), DynamoDB (key-value) | Aurora Serverless v1 (cold start) |
| Caching | ElastiCache Redis | Self-managed Redis on EC2 |
| Secrets | Secrets Manager or Parameter Store | Env vars in task definitions |
| Events | EventBridge | SNS fan-out for complex routing |
Red flags
- IAM policy with
"Action": "*"or"Resource": "*". - S3 bucket without explicit public access block.
- RDS without multi-AZ in production.
- Lambda with 15-minute timeout on critical path.
- No encryption at rest on any data store.
- No CloudTrail or access logging.
- Cost estimate missing from design doc.
Deep evaluation checklist
- Service decomposition and responsibilities.
- IAM — least privilege? trust boundaries explicit? cross-account?
- Networking — VPC, subnets, security groups, endpoints vs NAT.
- Queue/event semantics — at-least-once? ordering? DLQ?
- Data durability — backup, point-in-time recovery, cross-region?
- Availability — multi-AZ? failover tested? health checks meaningful?
- Secrets — rotation? scoped? auditable?
- Cost — top 3 cost drivers identified? reserved/spot where appropriate?
- Observability — CloudWatch, X-Ray, or OTel? alerts actionable?
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.
- 6d ago First seen · 59 lines · 27 tokens per session scan A daa78e8c9587
aws-production-systems is a skill published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 616 once invoked, about $0.0001 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 skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…