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/srstomp/pokayokay/cloud-infrastructurenpx skills add srstomp/pokayokay --skill cloud-infrastructuregit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/cloud-infrastructure)<a href="https://agentmods.dev/skills/srstomp/pokayokay/cloud-infrastructure"><img src="https://agentmods.dev/badge/skills/srstomp/pokayokay/cloud-infrastructure.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.00046 | $0.00606 |
| Opus 5 | $0.00023 | $0.00303 |
| Sonnet 5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
cloud-infrastructure 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Infrastructure
Design and provision cloud infrastructure with AWS-primary patterns and cloud-agnostic naming for portability.
Decision Framework
New service/workload?
├── Stateless, event-driven, <15min → Serverless (Lambda + API GW)
├── Long-running, stateful, predictable → Containers (ECS Fargate)
├── Kubernetes-native, multi-cloud → Orchestration (EKS)
└── Static content, CDN → Storage (S3 + CloudFront)
Database needs?
├── Key-value, <1ms, scale-to-zero → DynamoDB
├── Relational, complex queries → RDS/Aurora
├── Document store, flexible schema → DocumentDB
└── Cache, sessions, pub/sub → ElastiCache (Redis)
IaC approach?
├── AWS-only, type-safe → CDK (TypeScript)
├── Multi-cloud, declarative → Terraform
└── Simple, YAML → CloudFormation
When NOT to Use
- CI/CD pipelines: Use
ci-cdskill for pipeline config (CodePipeline, GitHub Actions) - Database schema design: Use
database-designskill for schema/migrations/queries - Application-level monitoring: Use
observabilityskill for application metrics/logs/traces
References
| File | Use When |
|---|---|
references/service-selection.md |
Choosing between AWS compute, database, or messaging services |
references/cdk-patterns.md |
Writing CDK constructs, organizing stacks, L1/L2/L3 patterns |
references/serverless-patterns.md |
Building Lambda functions, API Gateway, Step Functions, event-driven |
references/container-patterns.md |
ECS Fargate task definitions, service discovery, health checks |
references/iam-and-security.md |
IAM policies, security groups, VPC design, least privilege |
references/storage-and-cdn.md |
S3 configuration, CloudFront distributions, caching strategies |
references/database-selection.md |
DynamoDB patterns, RDS/Aurora configuration, managed DB comparison |
references/cost-optimization.md |
Right-sizing, reserved capacity, cost estimation, billing alerts |
Runtime Notes
- Claude Code: dispatch yokay-implementer via the Task tool with
subagent_type: "pokayokay:yokay-implementer". - Codex: there is no subagent dispatch. Execute the agent's role inline — read the corresponding
agents/yokay-<name>.mdand follow its Behavioral Defaults, Critical Rules, and Output Contract directly in the current session.
What ships with it
8 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.
- references/cdk-patterns.md 5.1 KB
- references/container-patterns.md 4.7 KB
- references/cost-optimization.md 4.9 KB
- references/database-selection.md 6.0 KB
- references/iam-and-security.md 4.9 KB
- references/serverless-patterns.md 5.4 KB
- references/service-selection.md 4.5 KB
- references/storage-and-cdn.md 5.2 KB
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 · 54 lines · 46 tokens per session scan A d7d1b4e1254f
cloud-infrastructure is a skill published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 606 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-31.
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…