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 azure-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/azure-iac-and-deployment)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/azure-iac-and-deployment"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-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/azure-iac-and-deployment"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-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.00074 | $0.02942 |
| Opus 5 | $0.00037 | $0.01471 |
| Sonnet 5 | $0.00015 | $0.00588 |
| Haiku 4.5 | $0.00007 | $0.00294 |
Grade A, and why
azure-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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Infrastructure-as-Code and Deployment
When to use
- Greenfield project — choosing between Bicep and Terraform for Azure resources.
- Inheriting portal-built infrastructure that needs to come into code.
- Designing a CI/CD pipeline for application and infrastructure changes.
- Hardening a release for safe rollout and rollback.
- Reviewing an existing IaC repo for drift, secret hygiene, and state management.
IaC tool — picking one
| Tool | Pick when |
|---|---|
| Bicep | Azure-only shop; team wants first-class Azure type safety, no state file, and ARM-native idempotency. Recommended default for Azure-focused teams. |
Terraform / OpenTofu (hashicorp/azurerm) |
Multi-cloud, multi-provider (Azure + Cloudflare DNS + GitHub Actions + Datadog), or org-wide standard already in place. Best module ecosystem; plan / apply workflow is well-understood by most platform teams. |
Terraform (Azure/azapi) |
Using azurerm but need a resource not yet supported — azapi wraps the ARM REST API directly. Pair azurerm + azapi in the same configuration; azapi fills the gaps. |
| ARM templates (JSON) | Legacy — you are inheriting existing ARM templates or deploying to an environment where only ARM is accepted (some GovCloud / sovereign cloud restrictions). Prefer Bicep over raw ARM for all new authoring; Bicep compiles to ARM and is fully equivalent. |
| Deployment Stacks | Azure-native stack lifecycle management: creates a Stack that owns all its resources and can delete orphaned resources on update. Complements Bicep; no equivalent in Terraform yet. Use for greenfield environments where you want ARM-managed cleanup. |
| Pulumi | Same niche as Bicep / Terraform but with a general-purpose language (TypeScript, Python, Go). Pick if the team strongly prefers a real programming language over HCL or Bicep DSL. |
Mixed tools are acceptable with clean boundaries: Bicep for Azure foundations (VNet, Key Vault, RBAC), Terraform for multi-cloud integrations (DNS, GitHub, monitoring SaaS). Avoid Terraform managing an AKS cluster that deploys Helm charts that deploy Bicep — pick a boundary and hold it.
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 · 142 lines · 74 tokens per session scan A 4aed7d971ecd
azure-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 74 tokens to every session and 2,942 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-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
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.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.