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/roboco-io/plugins/aws-well-architectednpx skills add roboco-io/plugins --skill aws-well-architectedgit clone --depth 1 https://github.com/roboco-io/pluginsWrote 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/roboco-io/plugins/aws-well-architected)<a href="https://agentmods.dev/skills/roboco-io/plugins/aws-well-architected"><img src="https://agentmods.dev/badge/skills/roboco-io/plugins/aws-well-architected.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 | $0.00051 | $0.01847 |
| Opus 5 | $0.00026 | $0.00924 |
| Sonnet 5 | $0.00010 | $0.00369 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade A, and why
aws-well-architected 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 3d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Well-Architected Review Skill
AWS Well-Architected Framework 기반의 IaC 코드 리뷰를 수행합니다. 이 스킬은 오케스트레이터로서 6개 Pillar별 스킬을 호출하고 통합 리포트를 생성합니다.
Framework Version
- 현재 지원: AWS Well-Architected Framework 2024-06-27
- 참고: AWS Well-Architected Framework
6 Pillars
| Pillar | 스킬 | 설명 |
|---|---|---|
| Operational Excellence | aws-wa-operational-excellence |
운영 효율성, 모니터링, 지속적 개선 |
| Security | aws-wa-security |
데이터 보호, ID/접근 관리, 탐지 제어 |
| Reliability | aws-wa-reliability |
장애 복구, 확장성, 고가용성 |
| Performance Efficiency | aws-wa-performance |
리소스 효율, 적정 규모, 성능 모니터링 |
| Cost Optimization | aws-wa-cost |
비용 최적화, 탄력성, 구매 옵션 |
| Sustainability | aws-wa-sustainability |
환경 영향 최소화, 에너지 효율 |
지원 IaC 플랫폼
| 플랫폼 | 파일 확장자 |
|---|---|
| Terraform | .tf, .tfvars |
| CloudFormation | .yaml, .yml, .json |
| AWS CDK | .ts, .py, .java |
| Pulumi | .ts, .py, .go, .yaml |
실행 프로세스
1. 초기 설정 확인
프로젝트 루트에서 .wa-config.yaml 확인:
trigger:
auto: true
paths:
- "infrastructure/**/*.tf"
- "cdk/**/*.ts"
language: ko # ko | en
pillars: all # all | security,reliability | custom
설정 파일이 없으면 AskUserQuestion으로 설정 수집.
2. 리뷰 범위 결정
AskUserQuestion으로 확인:
"리뷰 범위를 선택해주세요."
1. 전체 리포지토리 (권장)
2. 변경된 파일만 (git diff)
3. 특정 디렉토리 지정
3. Pillar 선택
AskUserQuestion으로 확인:
"어떤 Pillar를 리뷰할까요?"
1. 전체 6 Pillars (권장)
2. Security + Reliability만 (빠른 리뷰)
3. 직접 선택
4. 컨텍스트 인터뷰 (필요 시)
IaC 코드만으로 판단 어려운 경우:
"더 정확한 리뷰를 위해 몇 가지 질문을 드려도 될까요?"
1. 예, 인터뷰 진행
2. 아니오, 확인 가능한 범위만 리뷰
인터뷰 질문 예시:
- 규정 준수 요구사항 (HIPAA, PCI-DSS, GDPR)
- RTO/RPO 정의 여부
- 월간 AWS 예산
- 트래픽 패턴
5. 단계별 리뷰 실행
대규모 리포지토리인 경우:
- 1단계: Critical 리스크만 스캔
- 2단계: High 리스크 추가
- 3단계: Medium/Low 포함 전체
6. Pillar별 스킬 호출
선택된 Pillar에 해당하는 스킬 참조:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 230 lines · 51 tokens per session scan A 38c87e9b04c6
aws-well-architected is a skill published in the GitHub repository roboco-io/plugins (21 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,847 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…