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-costnpx skills add roboco-io/plugins --skill aws-wa-costgit 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-wa-cost)<a href="https://agentmods.dev/skills/roboco-io/plugins/aws-wa-cost"><img src="https://agentmods.dev/badge/skills/roboco-io/plugins/aws-wa-cost.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.00033 | $0.01388 |
| Opus 5 | $0.00016 | $0.00694 |
| Sonnet 5 | $0.00007 | $0.00278 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
aws-wa-cost 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 4d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost Optimization Pillar
비용 최적화, 탄력성, 구매 옵션 관점에서 IaC 코드를 검토합니다.
핵심 원칙
- 클라우드 재무 관리 구현: Cost Explorer, 예산
- 소비 모델 채택: 사용한 만큼 지불
- 전체 효율성 측정: 비용 대비 비즈니스 가치
- 차별화되지 않는 과중한 작업 중단: 관리형 서비스 활용
- 비용 분석 및 귀속: 태그 기반 비용 할당
검토 항목
COST-01: 과도한 인스턴스 크기
| 심각도 | 탐지 유형 |
|---|---|
| Medium | 자동 탐지 |
검토 내용: 개발/테스트 환경에서 과도한 인스턴스 크기 사용 여부
Terraform 패턴:
# 검토 필요 - 개발 환경에 큰 인스턴스
resource "aws_instance" "dev" {
instance_type = "m5.4xlarge"
tags = {
Environment = "dev"
}
}
# 권장 - 환경에 맞는 크기
resource "aws_instance" "dev" {
instance_type = "t3.medium"
tags = {
Environment = "dev"
}
}
COST-02: S3 스토리지 클래스
| 심각도 | 탐지 유형 |
|---|---|
| Low | 자동 탐지 |
검토 내용: Intelligent-Tiering, Glacier 활용 여부
Terraform 패턴:
# 권장 - Intelligent-Tiering
resource "aws_s3_bucket_intelligent_tiering_configuration" "good" {
bucket = aws_s3_bucket.example.id
name = "EntireBucket"
tiering {
access_tier = "DEEP_ARCHIVE_ACCESS"
days = 180
}
}
# 권장 - 수명 주기 정책
resource "aws_s3_bucket_lifecycle_configuration" "good" {
bucket = aws_s3_bucket.example.id
rule {
id = "archive"
status = "Enabled"
transition {
days = 90
storage_class = "GLACIER"
}
}
}
COST-03: 미사용 리소스
| 심각도 | 탐지 유형 |
|---|---|
| Medium | 자동 탐지 |
검토 내용: 미사용 EIP, 볼륨, 스냅샷 등 확인
주의 항목:
- 연결되지 않은 Elastic IP (비용 발생)
- 연결되지 않은 EBS 볼륨
- 오래된 스냅샷
COST-04: 항상 실행되는 개발 환경
| 심각도 | 탐지 유형 |
|---|---|
| Medium | 자동 탐지 |
검토 내용: 개발/테스트 환경이 24/7 실행되고 있는지 확인
Terraform 패턴:
# 권장 - 예약된 스케일링
resource "aws_autoscaling_schedule" "scale_down" {
scheduled_action_name = "scale-down-evening"
min_size = 0
max_size = 0
desired_capacity = 0
recurrence = "0 19 * * MON-FRI" # 저녁 7시
autoscaling_group_name = aws_autoscaling_group.dev.name
}
COST-05: Reserved Instance / Savings Plan
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.
- 4d ago First seen · 200 lines · 33 tokens per session scan A 0502c41fd673
aws-wa-cost is a skill published in the GitHub repository roboco-io/plugins (21 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,388 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.
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…