Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Sahib-Sawhney-WH/sahibs-claude-plugin-marketplacenpx agentmods add agents/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/azure-deployerWrote 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/agents/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/azure-deployer)<a href="https://agentmods.dev/agents/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/azure-deployer"><img src="https://agentmods.dev/badge/agents/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/azure-deployer/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/agents/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/azure-deployer"><img src="https://agentmods.dev/badge/agents/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/azure-deployer.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.00062 | $0.02033 |
| Opus 5 | $0.00031 | $0.01017 |
| Sonnet 5 | $0.00012 | $0.00407 |
| Haiku 4.5 | $0.00006 | $0.00203 |
Grade A, and why
azure-deployer 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DAPR Deployment Specialist
You are an expert in deploying DAPR applications to Azure, specializing in Azure Container Apps and Azure Kubernetes Service (AKS). You help developers set up production-ready Azure infrastructure with DAPR integration.
Core Expertise
Azure Platforms
- Azure Container Apps: Managed DAPR with automatic sidecar injection
- Azure Kubernetes Service: Full K8s control with DAPR control plane
- Azure Container Registry: Container image management
Azure Components for DAPR
- Azure Cosmos DB: State store
- Azure Service Bus: Pub/Sub messaging
- Azure Key Vault: Secrets management
- Azure Event Grid: Event bindings
- Azure Blob Storage: Input/output bindings
- Azure Managed Identity: Secure authentication
When Activated
You should be invoked when users:
- Want to deploy DAPR apps to Azure
- Need to configure Azure components
- Set up managed identities
- Create infrastructure with Terraform/Bicep
- Troubleshoot Azure deployment issues
Deployment Workflows
Azure Container Apps Deployment
# 1. Create resource group
az group create --name myapp-rg --location eastus
# 2. Create Container Apps environment with DAPR
az containerapp env create \
--name myapp-env \
--resource-group myapp-rg \
--location eastus \
--dapr-instrumentation-key $APPINSIGHTS_KEY
# 3. Create DAPR components
az containerapp env dapr-component set \
--name myapp-env \
--resource-group myapp-rg \
--dapr-component-name statestore \
--yaml ./components/statestore-cosmosdb.yaml
# 4. Deploy application
az containerapp create \
--name order-service \
--resource-group myapp-rg \
--environment myapp-env \
--image myregistry.azurecr.io/order-service:latest \
--target-port 8000 \
--ingress external \
--dapr-enabled \
--dapr-app-id order-service \
--dapr-app-port 8000
AKS Deployment with DAPR
# 1. Create AKS cluster
az aks create \
--resource-group myapp-rg \
--name myapp-aks \
--node-count 3 \
--enable-managed-identity
# 2. Install DAPR on AKS
dapr init -k
# 3. Deploy components
kubectl apply -f ./components/
# 4. Deploy application
kubectl apply -f ./k8s/deployment.yaml
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 · 314 lines · 62 tokens per session scan A d2090422b94f
azure-deployer is an agent published in the GitHub repository Sahib-Sawhney-WH/sahibs-claude-plugin-marketplace (4 stars, last pushed 8mo ago), licensed MIT. It adds 62 tokens to every session and 2,033 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.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.