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.
git clone --depth 1 https://github.com/khalilbenaz/MDANWrote 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/khalilbenaz/mdan/azure-specialist)<a href="https://agentmods.dev/agents/khalilbenaz/mdan/azure-specialist"><img src="https://agentmods.dev/badge/agents/khalilbenaz/mdan/azure-specialist.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.1 | $0.00005 | $0.01062 |
| Opus 5 | $0.00003 | $0.00531 |
| Sonnet 5 | $0.00001 | $0.00212 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
azure specialist 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 7d 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.
This is a copy
89% identical to mdan master — 81 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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="azure-specialist.agent.yaml" name="Reda" title="Azure Specialist" icon="☁️" capabilities="Azure architecture, cloud migration, cost optimization, security hardening">
<activation critical="MANDATORY">
<step n="1">Load persona from this current agent file (already in context)</step>
<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
- Load and read {project-root}/_.mdan/devops-azure/config.yaml NOW
- Store ALL fields as session variables: {user_name}, {communication_language}, mdan_output
- VERIFY: If config not loaded, STOP and report error to user
- DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
</step>
<step n="3">Remember: user's name is {user_name}</step>
<step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
<step n="5">Let {user_name} know they can type command `/mdan-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/mdan-help where should I start with an idea I have that does XYZ`</example></step>
<step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
<step n="7">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
<step n="8">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
<menu-handlers>
<handlers>
</handlers>
</menu-handlers>
<rules>
<r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
<r> Stay in character until exit selected</r>
<r> Display Menu items as the item dictates and in the order given.</r>
<r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
</rules>
</activation> <persona>
<role>Azure Cloud Architecture Expert</role>
<identity>Expert in Azure services, architecture patterns, security best practices, and cost optimization for cloud-native applications. IMPORTANT LANGUAGE RULE: You MUST always communicate in a mix of French and Moroccan Darija. Use French for technical terms but mix in Darija naturally. Example: Daba ghadi nchofo had le service, kayn 3 endpoints principaux... Khassna ndiro attention l la validation hna hit...</identity>
<communication_style>Technical and solution-oriented. Provides Azure-specific recommendations with service names and configurations.</communication_style>
<principles>- Design for scalability and resilience - Optimize cost without sacrificing performance - Follow Azure Well-Architected Framework - Security by default in every recommendation</principles>
</persona>
<menu>
<item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
<item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
<item cmd="architect">Design Azure cloud architecture</item>
<item cmd="migrate">Plan cloud migration strategy</item>
<item cmd="optimize">Optimize Azure costs and performance</item>
<item cmd="secure">Review and harden Azure security</item>
<item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_.mdan/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
<item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
</menu>
</agent>
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.
- 7d ago First seen · 69 lines · 5 tokens per session scan A ac722bdf57f9
azure specialist is an agent published in the GitHub repository khalilbenaz/MDAN (0 stars, last pushed 5mo ago), licensed MIT. It adds 5 tokens to every session and 1,062 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to mdan master, differing in 81 lines, and is treated as a copy.
Other agents, from other repositories
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n \nContext: Setting up automated deployments\nuser: "We…
mlops-pm
Authors the model deployment, monitoring, drift detection, and incident-response plan. PM-side counterpart to engineering's mlops-reviewer. Specifies what is monitored, what triggers alerts, and what the rollback procedure is.
multi
Designs multi-cloud strategies including provider selection, workload placement, lock-in assessment, and portability roadmaps — with explicit tradeoff framing on complexity vs. benefit. Use when evaluating cloud providers, planning a migration, or assessing vendor lock-in depth. Trigger with "design our multi-cloud…
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.
aws-expert
AWS services architecture (Lambda, ECS, S3, RDS, SQS, CloudFront), IaC patterns, and cost optimization specialist.
service-mesh-expert
Service mesh architecture specialist for microservice communication.