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 skills add jsgerman-oss/blackrim-nimbus-skills --skill aws-computegit clone --depth 1 https://github.com/jsgerman-oss/blackrim-nimbus-skillsWrote 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/jsgerman-oss/blackrim-nimbus-skills/aws-compute)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/aws-compute"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/aws-compute/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/jsgerman-oss/blackrim-nimbus-skills/aws-compute"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/aws-compute.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.00058 | $0.01783 |
| Opus 5 | $0.00029 | $0.00892 |
| Sonnet 5 | $0.00012 | $0.00357 |
| Haiku 4.5 | $0.00006 | $0.00178 |
Grade A, and why
aws-compute 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 12d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Compute
When to use
- Designing a new workload and choosing between serverless and container / VM compute.
- Tuning Lambda memory / timeout / concurrency, or chasing cold-start latency.
- Right-sizing ECS task definitions or EC2 instance families.
- Deciding ECS vs EKS for a containerized workload.
- Reviewing autoscaling, capacity, and warm-pool configuration.
- Auditing IAM execution roles attached to compute.
Decision tree
- Event-driven, < 15 min, irregular load, no persistent connections → Lambda.
- Long-running HTTP service, container-friendly, no Kubernetes investment → App Runner or ECS / Fargate behind ALB.
- Container fleet with sidecars, service mesh, GitOps, multi-tenant → EKS.
- GPU, FPGA, custom kernel, license-restricted AMI, > 14-day workloads → EC2.
- Throughput-oriented batch (rendering, genomics, ETL) → AWS Batch on Fargate or EC2 Spot.
Defaults
Lambda
- Architecture:
arm64(Graviton) unless a native dep is x86-only — ~20% cheaper, often faster. - Memory: start at 1024 MB, profile with Lambda Power Tuning, then trim.
- Timeout: set to 99p observed duration × 1.5; never the API-Gateway-mandated 29 s unless intentional.
- Concurrency: set reserved concurrency on every prod function to cap blast radius from a runaway upstream.
- VPC: only attach to a VPC if you actually need private resources — ENI cold-starts hurt.
- Packaging: container image if dependencies > 50 MB; otherwise zip with Lambda layers for shared deps.
- Idempotency: design every handler to be safely retried. SQS triggers will replay; EventBridge will redeliver.
ECS / Fargate
- Platform version:
LATEST, but pin in IaC so a new release doesn't surprise you mid-incident. - Task CPU / memory: pick from the supported pairs; over-provisioning memory is cheaper than CPU-bound throttling.
- Service discovery: AWS Cloud Map or service connect — avoid hand-rolled DNS.
- Deployment:
CODE_DEPLOYblue/green for any user-facing service;ECSrolling for back-of-house. - Health check grace period: at least 60 s for JVM / .NET, 30 s for Go / Node / Python.
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.
- 12d ago First seen · 113 lines · 58 tokens per session scan A 0d44092e1252
aws-compute is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 27d ago), licensed MIT. It adds 58 tokens to every session and 1,783 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…