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-iac-and-deploymentgit 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-iac-and-deployment)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/aws-iac-and-deployment"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/aws-iac-and-deployment/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-iac-and-deployment"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/aws-iac-and-deployment.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.00072 | $0.01762 |
| Opus 5 | $0.00036 | $0.00881 |
| Sonnet 5 | $0.00014 | $0.00352 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
aws-iac-and-deployment 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Infrastructure-as-Code and Deployment
When to use
- Greenfield project — picking an IaC tool.
- Inheriting console-built infrastructure that needs to come into code.
- Designing a CI/CD pipeline for app + infra.
- Hardening a release for safe rollout / rollback.
- Reviewing an existing IaC repo for drift, secrets, state hygiene.
IaC tool — picking one
| Tool | Pick when |
|---|---|
| AWS CDK (v2) | Team is comfortable in TypeScript / Python; you want first-class AWS abstractions and you'll stay AWS-only for the foreseeable future. |
| Terraform / OpenTofu | Multi-cloud, multi-provider (Cloudflare DNS + GitHub repos + AWS + ...), or you want a single tool across the org. Largest community, best module ecosystem. |
| AWS SAM | Lambda-heavy serverless app where 80% of IaC is functions + APIs + EventBridge. SAM CLI's local dev loop is the win. |
| CloudFormation (raw) | You already have huge CFN investment, or you're shipping to GovCloud / China and tooling pinning matters. Otherwise, prefer CDK over raw CFN. |
| Pulumi | Same niche as CDK but multi-cloud; pick if your team strongly prefers a real programming language over HCL. |
| CrossPlane | You want Kubernetes to be the control plane for cloud infra. Niche but powerful for platform teams. |
Mixed tools are fine but draw clean boundaries — Terraform for foundations (VPC, IAM, accounts), CDK for app stacks, SAM for serverless components. Resist Terraform-managing-an-EKS-cluster-that-deploys-CDK-stacks unless you really have to.
State management
- Terraform: S3 backend + DynamoDB lock table, separate state file per environment, KMS-encrypted.
- CDK / CloudFormation: state lives in CloudFormation itself; cross-stack refs via
Exports(sparingly) or SSM Parameter Store. - One workspace / stack per environment. Never
if env == "prod"branching inside a single stack — duplicate config beats lazy abstraction. - Stateful resources (RDS, S3, DynamoDB) in separate stacks from compute, with
DeletionPolicy: Retain/prevent_destroy = true.
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 · 121 lines · 72 tokens per session scan A bca3d131dfea
aws-iac-and-deployment is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 72 tokens to every session and 1,762 once invoked, about $0.0004 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
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
github-repo-setup
Use when bootstrapping a new repo's GitHub-side setup — branch protection / rulesets, deploy environments, environment secrets, OIDC cloud auth, or required reviewers — or whenever deploy workflows reference secrets. / environment: that don't exist yet. Captures the repo settings that make the feat → dev → main…
gitops-workflow
Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.