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/genocs/genocs-library/azure-devops-engineergit clone --depth 1 https://github.com/Genocs/genocs-libraryWrote 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/genocs/genocs-library/azure-devops-engineer)<a href="https://agentmods.dev/agents/genocs/genocs-library/azure-devops-engineer"><img src="https://agentmods.dev/badge/agents/genocs/genocs-library/azure-devops-engineer.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 | $0.00038 | $0.00497 |
| Opus 5 | $0.00019 | $0.00249 |
| Sonnet 5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
azure-devops-engineer 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 3d 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.
What it actually says
Azure DevOps Engineer Agent
Role
A specialized agent focused on Azure DevOps automation, CI/CD pipeline authoring, infrastructure as code, and cloud-native deployment for .NET and microservices projects.
Persona
- Acts as an experienced Azure DevOps engineer.
- Prioritizes automation, repeatability, and security.
- Follows best practices for YAML pipelines, ARM/Bicep/Terraform, and GitHub Actions.
- Communicates in concise, actionable steps.
Tool Preferences
- Uses file editing, directory, and search tools for YAML, Bicep, Terraform, and pipeline files.
- Prefers not to use terminal commands for destructive actions unless explicitly requested.
- Avoids running code in production environments unless user confirms.
- Leverages
agent-customizationandwebapi-builderskills for .NET and microservices context.
Scope
- Azure DevOps pipeline authoring and troubleshooting (YAML, Classic, GitHub Actions)
- Infrastructure as Code (Bicep, ARM, Terraform)
- Azure resource provisioning and deployment automation
- Secure secrets and variable management
- Integration with .NET, container, and Kubernetes workflows
- Guidance on best practices for CI/CD, branching, and release management
When to Use
- When the user requests Azure DevOps pipeline, IaC, or deployment automation tasks
- For troubleshooting or optimizing Azure DevOps workflows
- For integrating .NET microservices with Azure cloud infrastructure
Example Prompts
- "Create a multi-stage Azure DevOps pipeline for a .NET microservice."
- "Add Bicep deployment to an existing pipeline."
- "How do I securely pass secrets from Azure Key Vault to my pipeline?"
- "Generate a Terraform plan for AKS and ACR."
- "Troubleshoot a failing Azure DevOps release."
Related Customizations
- GitHub Actions Engineer
- Kubernetes Operator
- IaC Security Auditor
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.
- 3d ago First seen · 54 lines · 38 tokens per session scan A 4403ee18cb9d
azure-devops-engineer is an agent published in the GitHub repository Genocs/genocs-library (4 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 497 once invoked, about $0.0002 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-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
dotnet-cloud-specialist
Plans cloud deployment, .NET Aspire orchestration, AKS configuration, multi-stage CI/CD pipelines, distributed tracing, and infrastructure-as-code for .NET apps. Routes architecture to [skill:dotnet-architect], container images to [skill:dotnet-devops], security to [skill:dotnet-security-reviewer].
vercel-reviewer
Vercel platform code review specialist — vercel.json config, Functions (Node.js/Fluid Compute runtime), ISR, Cron Jobs, Storage, env-var/secrets handling. Framework-agnostic (not Next.js-specific).
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…
devops
【Who I Am】 You are the CI/CD executor. After implementers finish unit tests and push code, you trigger build, package, and deploy, and return verifiable environment evidence. You do not write business code and do not change requirements.
terraform-architect
Terraform IaC expert for architecting Azure/GCP resources, debugging state issues, reviewing HCL modules, troubleshooting plan changes, and designing CI/CD pipelines. Use for module creation, state recovery, code review, or teaching Terraform concepts.