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-wa-reliabilitynpx skills add roboco-io/plugins --skill aws-wa-reliabilitygit clone --depth 1 https://github.com/roboco-io/pluginsWhat 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.00034 | $0.01195 |
| Opus 5 | $0.00017 | $0.00598 |
| Sonnet 5 | $0.00007 | $0.00239 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
aws-wa-reliability 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.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reliability Pillar
장애 복구, 확장성, 고가용성 관점에서 IaC 코드를 검토합니다.
핵심 원칙
- 장애로부터 자동 복구: Auto Scaling, Health Check
- 복구 절차 테스트: DR 테스트
- 수평 확장: Multi-AZ, Auto Scaling
- 용량 추측 중단: 메트릭 기반 스케일링
- 변경 관리 자동화: IaC, CI/CD
검토 항목
REL-01: Multi-AZ 배포
| 심각도 | 탐지 유형 |
|---|---|
| Critical | 자동 탐지 |
검토 내용: 주요 리소스가 Multi-AZ로 배포되어 있는지 확인
Terraform 패턴:
# 취약 - 단일 AZ
resource "aws_db_instance" "bad" {
multi_az = false
}
# 안전 - Multi-AZ
resource "aws_db_instance" "good" {
multi_az = true
}
REL-02: Auto Scaling
| 심각도 | 탐지 유형 |
|---|---|
| High | 자동 탐지 |
검토 내용: Auto Scaling Group이 설정되어 있는지 확인
Terraform 패턴:
# 안전 - Auto Scaling 설정
resource "aws_autoscaling_group" "good" {
min_size = 2
max_size = 10
desired_capacity = 2
health_check_type = "ELB"
health_check_grace_period = 300
}
REL-03: 백업 설정
| 심각도 | 탐지 유형 |
|---|---|
| High | 자동 탐지 |
검토 내용: RDS, EBS 등의 자동 백업이 설정되어 있는지 확인
Terraform 패턴:
# 취약 - 백업 비활성화
resource "aws_db_instance" "bad" {
backup_retention_period = 0
}
# 안전 - 백업 활성화
resource "aws_db_instance" "good" {
backup_retention_period = 7
backup_window = "03:00-04:00"
}
REL-04: Health Check
| 심각도 | 탐지 유형 |
|---|---|
| High | 자동 탐지 |
검토 내용: ALB/NLB에 적절한 Health Check가 설정되어 있는지 확인
Terraform 패턴:
# 안전 - Health Check 설정
resource "aws_lb_target_group" "good" {
health_check {
enabled = true
healthy_threshold = 2
unhealthy_threshold = 3
timeout = 5
interval = 30
path = "/health"
matcher = "200"
}
}
REL-05: S3 복제
| 심각도 | 탐지 유형 |
|---|---|
| Medium | 자동 탐지 |
검토 내용: 중요 데이터에 Cross-Region Replication이 설정되어 있는지 확인
REL-06: 단일 NAT Gateway
| 심각도 | 탐지 유형 |
|---|---|
| Medium | 자동 탐지 |
검토 내용: 각 AZ에 NAT Gateway가 있는지 확인 (단일 실패 지점 방지)
What ships with it
4 files 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.
- 2d ago First seen · 180 lines · 34 tokens per session scan A 93f5d1c71104
aws-wa-reliability is a skill published in the GitHub repository roboco-io/plugins (21 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,195 once invoked, about $0.0002 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.