430-azure

430-azure is a cursor rule for Cursor from d-padmanabhan/agent-engineering-handbook. It costs 20 tokens per session (5,150 once invoked), scanned A, original, MIT.

A set of recommended patterns for building and naming Microsoft Azure cloud resources. Azure is Microsoft's platform for hosting applications, data, and other online services.

In plain words
What is it for?
Use it when designing Azure systems, writing Bicep infrastructure templates, naming resources, or planning security and reliability.
Why use it?
It helps keep Azure infrastructure consistent, secure, easier to manage, and mindful of cost and availability.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when designing Azure systems, writing Bicep infrastructure templates, naming resources, or planning security and reliability.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/d-padmanabhan/agent-engineering-handbook/430-azure
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.

Clone the repo
git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbook

Made for: Cursor.

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 430-azure

README.md
[![agentmods](https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/430-azure.svg)](https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/430-azure)
Your own site
<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/430-azure"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/430-azure.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,150 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.00020 $0.05150
Opus 5 $0.00010 $0.02575
Sonnet 5 $0.00004 $0.01030
Haiku 4.5 $0.00002 $0.00515

Measured 7d ago against content hash 4dd6a0d20d32, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

430-azure 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 7d 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.

rules/430-azure.mdc · 882 lines

How it starts

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

Microsoft Azure Best Practices

Guiding Principles

  1. Cloud-Native Design: Leverage Azure-native services (App Service, Functions, Container Apps)
  2. Infrastructure as Code: Use Bicep over ARM templates, Terraform for multi-cloud
  3. Security by Default: Azure AD, Key Vault, Private Endpoints, NSGs
  4. Cost Optimization: Right-size resources, use reservations, implement auto-scaling
  5. High Availability: Availability Zones, geo-redundancy, Traffic Manager

Azure Resource Naming Convention

Standard Format

{resource-type}-{workload/app-name}-{environment}-{region}-{instance}

Examples

# Virtual Machine
vm-webserver-prod-eastus-001

# Storage Account (no hyphens, lowercase only, max 24 chars)
stwebprodeastus001

# App Service
app-webapp-prod-eastus-001

# Key Vault (max 24 chars)
kv-webapp-prod-eus-001

# Resource Group
rg-webapp-prod-eastus

# Virtual Network
vnet-webapp-prod-eastus-001

# Network Security Group
nsg-webapp-prod-eastus-001

# Azure SQL Database
sql-webapp-prod-eastus-001

Bicep Best Practices

Basic Bicep Template

@description('Environment name (dev, staging, prod)')
@allowed([
  'dev'
  'staging'
  'prod'
])
param environment string

@description('Azure region for resources')
param location string = resourceGroup().location

@description('Application name')
param appName string

@description('Tags for all resources')
param tags object = {
  Environment: environment
  ManagedBy: 'Bicep'
  Application: appName
}

// Storage Account
resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
  name: 'st${appName}${environment}${uniqueString(resourceGroup().id)}'
  location: location
  tags: tags
  sku: {
    name: 'Standard_LRS'
  }
  kind: 'StorageV2'
  properties: {
    minimumTlsVersion: 'TLS1_2'
    supportsHttpsTrafficOnly: true
    allowBlobPublicAccess: false
    networkAcls: {
      defaultAction: 'Deny'
      bypass: 'AzureServices'
    }
    encryption: {
      services: {
        blob: {
          enabled: true
        }
        file: {
          enabled: true
        }
      }
      keySource: 'Microsoft.Storage'
    }
  }
}

// App Service Plan
resource appServicePlan 'Microsoft.Web/serverfarms@2023-01-01' = {
  name: 'asp-${appName}-${environment}-${location}'
  location: location
  tags: tags
  sku: {
    name: environment == 'prod' ? 'P1v3' : 'B1'
    tier: environment == 'prod' ? 'PremiumV3' : 'Basic'
  }
  properties: {
    reserved: true // Linux
  }
}

// Web App
resource webApp 'Microsoft.Web/sites@2023-01-01' = {
  name: 'app-${appName}-${environment}-${location}'
  location: location
  tags: tags
  identity: {
    type: 'SystemAssigned'
  }
  properties: {
    serverFarmId: appServicePlan.id
    httpsOnly: true
    siteConfig: {
      linuxFxVersion: 'NODE|20-lts'
      minTlsVersion: '1.2'
      ftpsState: 'Disabled'
      alwaysOn: environment == 'prod'
      healthCheckPath: '/health'
      appSettings: [
        {
          name: 'WEBSITES_ENABLE_APP_SERVICE_STORAGE'
          value: 'false'
        }
        {
          name: 'ENVIRONMENT'
          value: environment
        }
      ]
    }
  }
}

// Outputs
output webAppName string = webApp.name
output webAppHostname string = webApp.properties.defaultHostName
output storageAccountName string = storageAccount.name

Read the full file on GitHub · 882 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. 7d ago First seen · 882 lines · 20 tokens per session scan A 4dd6a0d20d32

Subscribe to this mod's changes

430-azure is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 8d ago), licensed MIT. It adds 20 tokens to every session and 5,150 once invoked, about $0.0001 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.