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-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/azure-compute)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/azure-compute"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-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/azure-compute"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-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.00060 | $0.02496 |
| Opus 5 | $0.00030 | $0.01248 |
| Sonnet 5 | $0.00012 | $0.00499 |
| Haiku 4.5 | $0.00006 | $0.00250 |
Grade A, and why
azure-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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Compute
When to use
- Choosing between serverless, container, and VM-based compute for a new workload.
- Tuning Azure Functions plan type, memory, or cold-start behaviour.
- Right-sizing AKS node pools or App Service plans.
- Deciding between AKS, Container Apps, App Service, and Container Instances.
- Reviewing autoscaling, node-pool topology, and workload scheduling.
- Auditing Managed Identity assignments attached to compute resources.
Decision tree
- Event-driven, short bursts, variable load, no persistent connections — Azure Functions (Consumption or Flex Consumption).
- Long-running HTTP service, team wants managed containers without Kubernetes — Container Apps (serverless-scale) or App Service (plan-based, deterministic pricing).
- Container fleet with sidecars, GitOps, multi-tenant, custom CRDs, service mesh — AKS.
- Ephemeral sidecar jobs, ad-hoc tasks, no persistent pod lifecycle needed — Container Instances.
- GPU, custom kernel, license-restricted image, or 14-day+ stateful workloads — Azure VMs (v5 / v6 families).
- Throughput-intensive batch (rendering, genomics, ML training, ETL at scale) — Azure Batch on dedicated or Spot VMs.
Defaults
Azure Functions
- Plan: start with Flex Consumption for new workloads — granular per-instance scaling with always-ready instances available. Fall back to Premium for VNET integration + no cold-start requirements; Consumption only for true infrequent event processing.
- Runtime: pin the major version explicitly in
functionAppConfig; never rely on auto-upgrade. - Identity: system-assigned Managed Identity — no connection strings or storage account keys in app settings.
- Networking: deploy into a VNet-integrated subnet when the function needs private PaaS resources; delegate the subnet to
Microsoft.App/environmentsorMicrosoft.Web/serverFarmsas appropriate. - Idempotency: every trigger handler must be safely retried. Service Bus and Event Hubs triggers guarantee at-least-once delivery.
- Storage: the backing storage account uses private endpoint + Managed Identity authentication; disable shared-key access (
allowSharedKeyAccess: false).
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 · 137 lines · 60 tokens per session scan A 17646d607fa0
azure-compute is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 60 tokens to every session and 2,496 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
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and attached-provider inference. Covers basic through advanced multi-step workflows. Trigger keywords - openshell…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.