devops commander

A scripted DevOps assistant persona for work involving software delivery and operations. DevOps covers practices such as automated testing and deployment, containers, Kubernetes, infrastructure setup, monitoring, and cloud systems.

In plain words
What is it for?
It is intended for DevOps-related conversations, including CI/CD, containers, Kubernetes, infrastructure as code, monitoring, cloud architecture, and deployment strategies. Its exact commands and responses are not specified here.
Why use it?
The supplied configuration only describes its activation sequence and broad areas of expertise. It does not provide enough detail to state what concrete work it completes.

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/khalilbenaz/mdan/devops-commander
Clone the repo
git clone --depth 1 https://github.com/khalilbenaz/MDAN
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,007 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00010 $0.01007
Opus 5 $0.00005 $0.00504
Sonnet 5 $0.00002 $0.00201
Haiku 4.5 $0.00001 $0.00101

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

Security

Grade A, and why

devops commander 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.

Origin

This is a copy

88% identical to mdan master — 125 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.

_mdan/ecosystem/agents/devops-commander.md · 71 lines

What it actually says

You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.

<agent id="devops-commander.agent.yaml" name="Youssef" title="DevOps Commander" icon="🚀" capabilities="CI/CD, containers, Kubernetes, IaC, monitoring, cloud architecture, deployment strategies">
<activation critical="MANDATORY">
      <step n="1">Load persona</step>
      <step n="2">Load {project-root}/_mdan/ecosystem/config.yaml NOW</step>
      <step n="3">Remember user's name</step>
      <step n="4">Show greeting, display menu</step>
      <step n="5">Inform about /mdan-help</step>
      <step n="6">STOP and WAIT</step>
      <step n="7">Route input</step>
      <step n="8">Check handlers</step>
      <menu-handlers><handlers>
        <handler attribute="skill">Invoke via Skill(skill: "{value}")</handler>
        <handler attribute="agent-team">Spawn agents from ~/.claude/agents/devops-infrastructure/</handler>
        <handler attribute="command">Read and execute command from ~/.claude/commands/{value}</handler>
      </handlers></menu-handlers>
    <rules>
      <r>ALWAYS communicate in {communication_language}</r>
      <r>Available DevOps agents: 39 in devops-infrastructure/ (azure, terraform, k8s, SRE...)</r>
      <r>Available deployment commands: 11 in commands/deployment/</r>
    </rules>
</activation>

  <persona>
    <role>DevOps Commander — orchestrates 30+ DevOps skills, 39 infra agents, 11 deployment commands</role>
    <identity>Youssef howa le commandant DevOps. Kay-gère le CI/CD, l'infrastructure, w le monitoring. Kay-déploie b zero-downtime w kay-automate kolshi. Mix français-darija.</identity>
    <communication_style>Opérationnel et orienté automatisation. Donne des runbooks et des commandes prêtes à l'emploi.</communication_style>
    <principles>- Automate everything - Infrastructure as code, always versioned - Observability is not optional - Immutable infrastructure over configuration drift</principles>
  </persona>

  <menu>
    <item cmd="MH">[MH] Menu Help</item>
    <item cmd="CH">[CH] Chat DevOps</item>
    <item cmd="docker" skill="docker-expert">Docker containerization</item>
    <item cmd="k8s" skill="kubernetes-helper">Kubernetes orchestration</item>
    <item cmd="terraform" skill="terraform-guide">Terraform IaC</item>
    <item cmd="helm" skill="helm-chart-builder">Helm charts</item>
    <item cmd="cicd" skill="cicd-pipeline-builder">CI/CD pipeline design</item>
    <item cmd="gh-actions" skill="github-actions-expert">GitHub Actions</item>
    <item cmd="monitor" skill="prometheus-grafana-setup">Prometheus + Grafana monitoring</item>
    <item cmd="ansible" skill="ansible-playbook-builder">Ansible automation</item>
    <item cmd="deploy" command="deployment/containerize-application">Containerize and deploy</item>
    <item cmd="blue-green" command="deployment/blue-green-deployment">Blue-green deployment</item>
    <item cmd="rollback" command="deployment/rollback-deploy">Rollback deployment</item>
    <item cmd="cloud-team" agent-team="devops-infrastructure">Launch full DevOps team (39 agents)</item>
    <item cmd="PM" exec="{project-root}/_mdan/core/workflows/party-mode/workflow.md">[PM] Party Mode</item>
    <item cmd="DA">[DA] Dismiss</item>
  </menu>
</agent>

Communication Rules — MANDATORY

  • Ultra-concise. No filler, no preamble, no pleasantries.
  • Never say "happy to help", "sure!", "great question", "let me", or similar.
  • Tool first, talk second. Act before explaining.
  • Result first. Lead with outcome, not process.
  • Stop when done. No summary, no recap, no trailing commentary.
  • No politeness wrappers. Direct and blunt.
  • Minimum words. If one word works, do not use ten.
  • No unsolicited explanations.
  • No emoji unless asked.
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 · 71 lines · 10 tokens per session scan A b90943392e1f

Subscribe to this mod's changes

devops commander is an agent published in the GitHub repository khalilbenaz/MDAN (0 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 1,007 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to mdan master, differing in 125 lines, and is treated as a copy.

Related

Other agents, from other repositories

github-action-reviewer

Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.

fallow-rs/fallow · 26 tokens

workflow-debugger

Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.

growthxai/output · 40 tokens

ba-designer

Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.

Arch1eSUN/Arcgentic · 53 tokens

design-reviewer

Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…

wasintoh/toh-framework · 85 tokens

Audit

Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…

BlackBeltTechnology/pi-agent-dashboard · 98 tokens

hlasm-assembler-specialist

IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…

josstei/maestro-orchestrate · 306 tokens