azure-observability-and-cost

azure-observability-and-cost is a skill for Claude Code from jsgerman-oss/blackrim-nimbus-skills. It costs 61 tokens per session (2,334 once invoked), scanned A, original, MIT.

A guide for setting up Azure monitoring and controlling Azure spending. Monitoring means collecting metrics, logs, and traces so you can understand application health and investigate failures or slowdowns.

In plain words
What is it for?
Adding telemetry and alerts, building service-level dashboards, diagnosing latency or errors, and reviewing discounts or other ways to reduce cloud costs.
Why use it?
It gives you a structured way to find performance, error, and cost regressions instead of relying on guesswork.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the cloud-azure plugin — 6 skills, 1 command, 2 agents shipped together

Good fit Adding telemetry and alerts, building service-level dashboards, diagnosing latency or errors, and reviewing discounts or other ways to reduce cloud costs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jsgerman-oss/blackrim-nimbus-skills/azure-observability-and-cost
Install

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.

Any agent
npx skills add jsgerman-oss/blackrim-nimbus-skills --skill azure-observability-and-cost
Clone the repo
git clone --depth 1 https://github.com/jsgerman-oss/blackrim-nimbus-skills

Made for: Claude Code.

Or install cloud-azure, the plugin that ships this one along with the rest of its 6 skills, 1 command, 2 agents.

Wrote 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.

agentmods badge for azure-observability-and-cost

README.md
[![agentmods](https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-observability-and-cost/github.svg)](https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/azure-observability-and-cost)
Your own site
<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/azure-observability-and-cost"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-observability-and-cost/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.

agentmods 80×15 button for azure-observability-and-cost

Your own site · 80×15
<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/azure-observability-and-cost"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/azure-observability-and-cost.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,334 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.02334
Opus 5 $0.00030 $0.01167
Sonnet 5 $0.00012 $0.00467
Haiku 4.5 $0.00006 $0.00233

Measured 12d ago against content hash 2fb61d7b497d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

azure-observability-and-cost 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.

cloud-azure/skills/azure-observability-and-cost/SKILL.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Azure Observability and Cost

When to use

  • Setting up metrics, logs, and traces for a new Azure service.
  • Building an SLO dashboard or wiring an alert to an on-call channel.
  • Diagnosing a latency, error-rate, or cost regression.
  • Negotiating a Reservation or Savings Plan commitment.
  • Running a quarterly cloud cost review.

Observability pillars

Pillar Service
Metrics Azure Monitor Metrics + platform metrics per resource
Logs Log Analytics workspace (KQL query surface)
Traces Application Insights (auto-instrumentation) or OpenTelemetry → Azure Monitor OTLP endpoint
Synthetics Application Insights Availability Tests (URL ping, multi-step)
Real user monitoring Application Insights JavaScript SDK or the Browser SDK
Service map Application Insights Application Map (dependency topology)

Defaults — every service

  • Structured JSON logs with a stable operationId / correlation ID field shared across the request chain.
  • Application Insights SDK or auto-instrumentation for request rate, failure rate, and response time — the three core signals. Use TelemetryClient or the OpenTelemetry Azure Monitor exporter.
  • Distributed tracing on, with the traceparent W3C header propagated end-to-end across microservices.
  • At least one alert per service tied to user-visible pain (HTTP 5xx rate, p95 response time, queue backlog, dead-letter count). Avoid alerting on raw CPU utilization alone.
  • Log retention: 30 days interactive (hot) in Log Analytics; extend to 90 days for security logs; ship to a Storage Account for archive retention > 90 days. The default 30-day retention is not an unbounded bill, but a 90-day retention upgrade costs ~$0.10/GB/mo and is worth it for incident investigations.
  • Diagnostic settings: every Azure resource must have a diagnostic setting routing logs and metrics to the central Log Analytics workspace. Enforce via Azure Policy.

Log Analytics workspace design

  • One workspace per environment (dev / stage / prod) is the simplest model. A centralized cross-subscription workspace is preferred when Sentinel is active or when Security Operations needs a single query pane.
  • Avoid too many workspaces: cross-workspace queries (workspace() function in KQL) work but add latency and complexity.
  • Data ingestion plan: Analytics plan for actively queried data; Basic plan for verbose diagnostic logs that are rarely queried but needed for compliance (reduces cost ~75% vs Analytics at the expense of limited query capability).
  • Commitment tiers: at 100+ GB/day ingestion, commitment tiers (100 GB, 200 GB, ...) are significantly cheaper than pay-as-you-go — calculate the break-even and buy the appropriate tier.
  • Table retention per table: set different retention on noisy tables (e.g., AzureDiagnostics from verbose sources) vs security tables (SecurityEvent, SigninLogs).

Read the full file on GitHub · 136 lines

Changes

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.

  1. 12d ago First seen · 136 lines · 61 tokens per session scan A 2fb61d7b497d

Subscribe to this mod's changes

azure-observability-and-cost is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 61 tokens to every session and 2,334 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.

Related

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…

google/skills · 83 tokens

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).

google/skills · 73 tokens

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…

google/skills · 181 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

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".

microsoft/skills · 78 tokens

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…

Jeffallan/claude-skills · 71 tokens