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.
git 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/commands/jsgerman-oss/blackrim-nimbus-skills/azure-scaffold-iac)<a href="https://agentmods.dev/commands/jsgerman-oss/blackrim-nimbus-skills/azure-scaffold-iac"><img src="https://agentmods.dev/badge/commands/jsgerman-oss/blackrim-nimbus-skills/azure-scaffold-iac/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/commands/jsgerman-oss/blackrim-nimbus-skills/azure-scaffold-iac"><img src="https://agentmods.dev/badge/commands/jsgerman-oss/blackrim-nimbus-skills/azure-scaffold-iac.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.00032 | $0.01733 |
| Opus 5 | $0.00016 | $0.00866 |
| Sonnet 5 | $0.00006 | $0.00347 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
azure-scaffold-iac 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Scaffold IaC
Scaffold a new Azure Infrastructure-as-Code project for a workload described as: $ARGUMENTS
What to do
-
Confirm the tool choice. Ask the user which IaC tool they want, with a one-line recommendation based on the workload description:
- Azure-only shop, team comfortable with a typed DSL, wants no state file → Bicep (recommended default for Azure-focused teams).
- Multi-cloud, multi-provider, or org already standardized on HCL → Terraform (
hashicorp/azurerm>= 4.x +Azure/azapi>= 2.x) or OpenTofu. - The user mentions ARM JSON templates → recommend Bicep instead. ARM JSON is legacy; Bicep compiles to ARM and is the recommended authoring surface for all new Azure IaC. Do not prescribe — recommend, then defer to the user.
-
Confirm scope with up to three questions if not obvious from the workload description:
- Single subscription, or multi-subscription with a Management Group hierarchy?
- Network: new VNet, or integrating with an existing hub-spoke topology?
- State: greenfield, or migrating from portal-built infrastructure (requires
az resource showimports)?
-
Generate the project skeleton in the current working directory or a subdirectory the user specifies. Every scaffold must include:
- Pinned tool / provider versions.
- Per-environment separation (
dev,stage,prod). - Remote, locked state (Terraform) or ARM-native state via Bicep.
- A
.gitignoreappropriate to the tool. - A
README.mdwith bootstrap and deploy / destroy commands. - At least one module / template set: networking (VNet + NSGs + private DNS zones) + a compute placeholder + a data placeholder.
- GitHub Actions (or Azure DevOps Pipeline YAML) with Workload Identity Federation for plan / apply, plus lint (
az bicep build --lint/tflint+checkov). - Tagging policy applied via a shared parameter or local variable (
Environment,Service,Owner,CostCenter).
-
Wire safe defaults. For every scaffold:
- Customer-managed key encryption at rest: Key Vault deployed first; CMK created; storage / database resources reference it.
- Managed Identity on every compute resource:
identity: { type: 'SystemAssigned' }in Bicep;identity { type = "SystemAssigned" }in Terraform. - Private endpoints for every PaaS data service;
publicNetworkAccess: 'Disabled'on storage and databases. - VNet with dedicated subnets for compute, data, and management; NSG on each subnet with default-deny inbound.
- Log Analytics workspace with bounded retention (30 days hot, 90 days for security tables); Application Insights linked to the same workspace.
- Diagnostic settings on every resource routing audit logs to the Log Analytics workspace.
- Azure Policy assignment for required tags; deny effect.
- Resource lock (
CanNotDelete) on every stateful production resource.
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 · 115 lines · 32 tokens per session scan A d7df5c247a26
azure-scaffold-iac is a command published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 27d ago), licensed MIT. It adds 32 tokens to every session and 1,733 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 commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.