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-ddos-protectiongit 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-ddos-protection)<a href="https://agentmods.dev/skills/vinayaklatthe/microsoft-security-skills/azure-ddos-protection"><img src="https://agentmods.dev/badge/skills/vinayaklatthe/microsoft-security-skills/azure-ddos-protection/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-ddos-protection"><img src="https://agentmods.dev/badge/skills/vinayaklatthe/microsoft-security-skills/azure-ddos-protection.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.00206 | $0.01866 |
| Opus 5 | $0.00103 | $0.00933 |
| Sonnet 5 | $0.00041 | $0.00373 |
| Haiku 4.5 | $0.00021 | $0.00187 |
Grade A, and why
azure-ddos-protection 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DDoS Protection
Azure DDoS Protection sits on the Microsoft global network and absorbs layer 3/4 volumetric and protocol attacks before they reach your workloads. The free Infrastructure Protection layer protects Azure as a platform; the paid DDoS Protection plans give you dedicated, profile-tuned mitigation, attack analytics, post-incident reports, cost protection, and Rapid Response support for your resources.
When to use
Public-facing workloads with a non-trivial cost-of-downtime: e-commerce, regulated financial APIs, multiplayer gaming, public-sector services, internet-facing AI APIs, streaming, and any campaign exposed to politically or commercially motivated DDoS.
Do not use this skill for application-layer (HTTP) attack mitigation alone
(azure-waf), Azure Firewall design (azure-firewall), or third-party DDoS appliance
patterns.
Tier selection
| Tier | Scope | Best for |
|---|---|---|
| Infrastructure Protection | Free, platform-level, no SLA, no analytics | Default for every workload |
| DDoS Network Protection | Per VNet, all public IPs in scope | Multi-IP workloads, large estates |
| DDoS IP Protection | Per public IP, granular | Small estates, cost-conscious, specific high-risk IP |
Pricing model differs: Network Protection is a flat fee per plan covering many resources; IP Protection is per-IP. Estate size flips the economics — model both before choosing.
Approach
-
Decide tier per workload.
- 50+ public IPs across multiple VNets → Network Protection on the relevant VNets.
- Specific internet-facing app on a single Standard public IP → IP Protection.
- Mixed → both, scoped appropriately.
-
Enable on the VNet (Network Protection) at deployment time. The platform begins traffic profiling immediately; it learns normal patterns over ~7 days and auto-tunes the per-IP mitigation policy. Mitigation accuracy improves the longer the profile runs.
-
Static thresholds are not a thing, by design. Mitigation is adaptive. Don't architect on the assumption of a fixed Mbps cap.
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 · 139 lines · 206 tokens per session scan A 9721279d7f1d
azure-ddos-protection is a skill published in the GitHub repository vinayaklatthe/microsoft-security-skills (173 stars, last pushed 2mo ago), licensed MIT. It adds 206 tokens to every session and 1,866 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.…