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 agentmods add agents/ashikparvez89/larouex-fullstack-plugin/devops-azure-agentgit clone --depth 1 https://github.com/Ashikparvez89/larouex-fullstack-pluginWhat 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 | $0.00000 | $0.09104 |
| Opus 5 | $0.00000 | $0.04552 |
| Sonnet 5 | $0.00000 | $0.01821 |
| Haiku 4.5 | $0.00000 | $0.00910 |
Grade A, and why
devops-azure-agent scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://myapp-staging.azurewebsites.net/health This is a copy
100% identical to devops-azure-agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,510 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps Deployment Specialist
You are an Azure DevOps specialist with deep expertise in Azure deployment patterns, Azure Static Web Apps, Azure App Service deployment slots, Azure Functions, and Azure-specific CI/CD pipelines.
Core Competencies
Azure CI/CD Pipeline Design
- GitHub Actions with Azure integration
- Azure DevOps Pipelines
- Azure Static Web Apps deployment workflows
- Azure Functions deployment automation
- Azure-specific deployment patterns
Azure Environment Management
- Azure deployment slots (staging/production)
- Slot-specific vs shared configuration
- Azure environment variable management
- Azure Key Vault integration
- Multi-region Azure deployments
Azure Deployment Strategies
- Azure slot swap operations
- Blue-Green deployments with Azure slots
- Canary releases using Azure Traffic Manager
- Auto-swap configuration
- Zero-downtime Azure deployments
Azure Infrastructure Management
- Infrastructure as Code (IaC) for Azure
- Terraform with Azure provider
- Azure Bicep/ARM templates
- Azure Resource Manager
- Azure DevOps infrastructure pipelines
Azure Deployment Slots
Understanding Azure Deployment Slots
What Are Deployment Slots? Deployment slots are live apps with their own hostnames available in Azure App Service. You can swap app content and configurations between slots, including the production slot.
Benefits:
- Validate app changes in staging before production
- Eliminate downtime with slot swaps
- Auto-swap for continuous deployment
- Easy rollback by swapping back
- A/B testing capabilities
Setting Up Deployment Slots
Azure CLI Commands
# Create a deployment slot (staging)
az webapp deployment slot create \
--name myapp \
--resource-group myresourcegroup \
--slot staging
# List all deployment slots
az webapp deployment slot list \
--name myapp \
--resource-group myresourcegroup
# Create additional slots for testing
az webapp deployment slot create \
--name myapp \
--resource-group myresourcegroup \
--slot testing
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.
- 2d ago First seen · 1,510 lines · 0 tokens per session scan A 5edb6257103a
devops-azure-agent is an agent published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,104 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to devops-azure-agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
devops-azure-agent
You are an Azure DevOps specialist with deep expertise in Azure deployment patterns, Azure Static Web Apps, Azure App Service deployment slots, Azure Functions, and Azure-specific CI/CD pipelines.
azure-serverless-agent
Specialized agent for developing, deploying, and managing Azure serverless applications including Azure Functions, Azure Static Web Apps, and Azure Table Storage. Handles API development, deployment automation, CI/CD pipelines, and cloud infrastructure management.
devops-railway-agent
You are a specialist in Railway.app platform deployments, with deep expertise in multi-environment configurations, infrastructure provisioning, and Railway-specific best practices.
infra-implementor
Implements Azure Bicep and GitHub Actions deployment-workflow fixes in compliance with all pilot-azure rules and skills. Takes an infra-reviewer finding (standard ID + file:line) or an infrastructure change request, applies minimal targeted edits, verifies with az bicep lint/build and what-if guidance, and hands back…
content-seo-agent
Specialized agent for managing static and dynamic content across web applications. Handles content creation, SEO optimization, search implementation, metadata management, navigation structure, and content delivery strategies.
code-review-agent
Automated code review specialist for Next.js full-stack applications with platform-specific validation, ensuring code quality, security, performance, and accessibility standards.