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 vinayaklatthe/microsoft-security-skills --skill azure-monitor-securitygit clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-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/vinayaklatthe/microsoft-security-skills/azure-monitor-security)<a href="https://agentmods.dev/skills/vinayaklatthe/microsoft-security-skills/azure-monitor-security"><img src="https://agentmods.dev/badge/skills/vinayaklatthe/microsoft-security-skills/azure-monitor-security/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/vinayaklatthe/microsoft-security-skills/azure-monitor-security"><img src="https://agentmods.dev/badge/skills/vinayaklatthe/microsoft-security-skills/azure-monitor-security.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.00201 | $0.02174 |
| Opus 5 | $0.00101 | $0.01087 |
| Sonnet 5 | $0.00040 | $0.00435 |
| Haiku 4.5 | $0.00020 | $0.00217 |
Grade A, and why
azure-monitor-security 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 13d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Monitor & Log Analytics for Security
Microsoft Sentinel runs on a Log Analytics workspace. Defender for Cloud, Defender XDR hunting tables, Activity logs, and Diagnostic settings also flow there. The workspace strategy decides whether your security telemetry is complete, compliant, and affordable — or two of three.
This skill covers the security-side decisions in workspace design: tiering, retention, DCRs, RBAC, and cost.
When to use
Designing or refactoring the Log Analytics workspace(s) that back Sentinel and the broader security telemetry estate.
Do not use this skill for Sentinel detection authoring
(sentinel-detection-engineering), App Insights instrumentation
(appinsights-instrumentation), or non-security observability.
Log table tiers — pick per table
| Tier | Query latency | Retention max | Use case |
|---|---|---|---|
| Analytics | Sub-second | 730 days interactive | Detections, hunting, dashboards |
| Basic | Seconds (KQL with limits) | 30 days interactive + archive | High-volume "search if needed" logs |
| Auxiliary | Slower / async | 12 months interactive | Low-touch compliance archive feeds |
| Archive (any tier) | Search-job recall | up to 12 years | Long-tail evidence, regulatory hold |
Microsoft has been re-naming/re-shaping these — verify current naming and pricing in your region before commit.
Approach
-
Workspace topology.
- Default: one Sentinel workspace per tenant for security signal — keeps correlation easy.
- Regional / sovereign: separate workspaces where data residency or sovereignty requires.
- Multi-workspace Sentinel: only when business reasons (M&A boundary, MSSP model) force it. Cross-workspace queries work but add complexity.
- Don't split per-team; that fragments correlation.
-
Use Azure Monitor Agent (AMA) for everything new. The Microsoft Monitoring Agent (MMA / Log Analytics agent) is retired. Migration paths via Defender for Cloud auto-provisioning and Sentinel solutions.
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.
- 13d ago First seen · 164 lines · 201 tokens per session scan A 46571810406f
azure-monitor-security is a skill published in the GitHub repository vinayaklatthe/microsoft-security-skills (173 stars, last pushed 2mo ago), licensed MIT. It adds 201 tokens to every session and 2,174 once invoked, about $0.0010 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-30.
Other skills, from other repositories
deepspeed
Expert guidance for distributed training with DeepSpeed - ZeRO optimization stages, pipeline parallelism, FP16/BF16/FP8, 1-bit Adam, sparse attention.
agents-sdk-provision
Use when provisioning Azure resources for a Microsoft Agents SDK application — including creating an Azure Bot Service resource, setting up Entra app registrations, configuring identity credentials (UserManagedIdentity, FederatedCredentials, or ClientSecret), adding a Teams channel, running Bicep deployments for SSO…
detecting-azure-service-principal-abuse
Detect and investigate Azure service principal abuse including privilege escalation, credential compromise, admin consent bypass, and unauthorized enumeration in Microsoft Entra ID environments.
detecting-azure-lateral-movement
Detect lateral movement in Azure AD/Entra ID environments using Microsoft Graph API audit logs, Azure Sentinel KQL hunting queries, and sign-in anomaly correlation to identify privilege escalation, token theft, and cross-tenant pivoting.
aspire
Build, upgrade, and operate Aspire 13.5.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting., DistributedApplication.CreateBuilder, apphost.mts…
azure-functions
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable Functions, bindings, or host configuration.…