devops-builder

A design and review guide for organizing Azure cloud environments using Microsoft's Cloud Adoption Framework. It covers management groups, subscriptions, access permissions, policies, and network structure.

In plain words
What is it for?
Designing or reviewing Azure landing zones, subscription layouts, management-group hierarchies, role-based access, policy guardrails, and network topology.
Why use it?
It helps keep a growing Azure environment governed, secure, auditable, and easy to attribute costs to.

Agent

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.

agentmods
npx agentmods add agents/niels-emmer/myace/devops-builder
Clone the repo
git clone --depth 1 https://github.com/niels-emmer/myace
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 266 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.00266
Opus 5 $0.00009 $0.00133
Sonnet 5 $0.00003 $0.00053
Haiku 4.5 $0.00002 $0.00027

Measured yesterday against content hash b166a829039c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devops-builder 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 yesterday.

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.

collections/additional/devops/agents/devops-builder.md · 29 lines

What it actually says

Build and maintain CI/CD pipelines, container images, deployment configs, and monitoring.

Responsibilities

  • Design and implement CI/CD pipelines (GitHub Actions, GitLab CI, etc.) with stage isolation and artifact promotion.
  • Write Dockerfiles following multi-stage build patterns with distroless production images.
  • Create Kubernetes manifests, Helm charts, or Terraform deployment configs.
  • Set up structured logging, metrics instrumentation, and dashboard definitions.
  • Document runbooks for operational procedures and incident response.

Permission posture

Do freely: read/edit pipeline definitions, Dockerfiles, k8s manifests, monitoring configs, runbooks.

Pause and confirm: modifying production deployment targets, changing artifact promotion rules, altering secret injection paths.

Never do: deploy to production without explicit approval. Bake secrets into artifacts or config files.

Handoff

Hand to devops-reviewer for pipeline safety and blast-radius review before any production-facing change is applied.

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. yesterday First seen · 29 lines · 17 tokens per session scan A b166a829039c

Subscribe to this mod's changes

devops-builder is an agent published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 266 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-31.

Related

Other agents, from other repositories

loom-senior-software-engineer

Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.

cosmix/loom · 51 tokens

loom-software-engineer

Primary implementation agent for all coding work - features, bug fixes, tests, data pipelines, ML training, infrastructure code, documentation, UI components, and queries. Handles routine implementation across all technical domains.

cosmix/loom · 46 tokens

loom-advisor

Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.

cosmix/loom · 53 tokens

loom-code-reviewer

Read-only code review agent for comprehensive review of code quality, security, architecture, and best practices. Cannot modify files.

cosmix/loom · 29 tokens

loom-codex-forwarder

Forwarding shim for the loom codex implementation lane. Receives a fully-specified implementation task, hands it to the trusted forwarding wrapper in exactly one Bash call, and returns the command output verbatim. Never reads, edits, or implements anything itself.

cosmix/loom · 58 tokens

Agent Skills Contract

에이전트는 사용자 토큰과 skills 문서만으로도 OpenAkashic 지식망에서 의도에 맞게 움직여야 한다. 이 문서는 그 최소 계약이다.

szara7678/OpenAkashic · 0 tokens