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.
git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/rules/d-padmanabhan/agent-engineering-handbook/430-azure)<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>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.00020 | $0.05150 |
| Opus 5 | $0.00010 | $0.02575 |
| Sonnet 5 | $0.00004 | $0.01030 |
| Haiku 4.5 | $0.00002 | $0.00515 |
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.
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
- Cloud-Native Design: Leverage Azure-native services (App Service, Functions, Container Apps)
- Infrastructure as Code: Use Bicep over ARM templates, Terraform for multi-cloud
- Security by Default: Azure AD, Key Vault, Private Endpoints, NSGs
- Cost Optimization: Right-size resources, use reservations, implement auto-scaling
- 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
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.
- 7d ago First seen · 882 lines · 20 tokens per session scan A 4dd6a0d20d32
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.
Other cursor rules, from other repositories
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.