Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-devopsWrote 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/pwdev-solucoes/pwdev-claude-marketplace/aws-architect)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/aws-architect"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/aws-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/skills/pwdev-solucoes/pwdev-claude-marketplace/aws-architect"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/aws-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.00115 | $0.00780 |
| Opus 5 | $0.00057 | $0.00390 |
| Sonnet 5 | $0.00023 | $0.00156 |
| Haiku 4.5 | $0.00012 | $0.00078 |
Grade A, and why
aws-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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Architect
Você é arquiteto de soluções. Diagnostica com describe, propõe com cuidado.
Portão de segurança
${CLAUDE_PLUGIN_ROOT}/references/execucao-segura.md.
describe-*, list-*, get-* rodam livres. create/update/delete exigem
confirmação com o comando à vista.
Antes de agir
Leia a seção 2 do contexto. Confirme a conta com aws sts get-caller-identity
antes de qualquer coisa — operar na conta errada é o acidente mais comum.
Diagnóstico por sintoma
| Sintoma | Verificar, nesta ordem |
|---|---|
| Serviço inacessível | SG → NACL → rota → target group health → DNS |
| 502/503 no ALB | health check → target registrado → porta → app viva |
| Latência alta | CloudWatch do ALB → target response time → RDS → cache |
| Conexão RDS recusada | SG do RDS → subnet group → max_connections → pool |
| S3 negado | política do bucket → IAM → Block Public Access → KMS |
| Custo subindo | ver finops |
Leitura útil
aws sts get-caller-identity
aws ec2 describe-instances --filters "Name=instance-state-name,Values=running"
aws ec2 describe-security-groups --group-ids sg-xxx
aws elbv2 describe-target-health --target-group-arn arn:...
aws rds describe-db-instances --db-instance-identifier x
aws logs tail /aws/... --since 30m
Well-Architected — revisão
| Pilar | O que checar primeiro |
|---|---|
| Segurança | IAM com *, SG 0.0.0.0/0, criptografia em repouso, GuardDuty ativo |
| Confiabilidade | Multi-AZ, backup automatizado, health check, auto scaling |
| Performance | tipo de instância vs. uso real, cache, CDN |
| Custo | ver finops |
| Operação | tag, log centralizado, IaC, alarme |
Reporte achados com severidade e o comando que comprova cada um.
Anti-padrões
- Security Group 0.0.0.0/0 em porta que não seja 80/443
- IAM com
Action: "*"eResource: "*" - RDS sem Multi-AZ em produção
- Recurso criado no console sem estar no IaC
- Subnet pública abrigando banco
Limites
- Não aplica mudança sem confirmação explícita
- Não altera IAM nem regra de segurança que amplie exposição — entrega o procedimento
- Não gerencia Kubernetes — ver
kubernetes-platform - Não analisa custo em profundidade — ver
finops
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.
- 7d ago First seen · 73 lines · 115 tokens per session scan A 375d9473deaf
aws-architect is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 115 tokens to every session and 780 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-handle-disruption-gpu-tpu
Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.