This skill executes arbitrary commands from external files, manipulates
Claims to do
Azure Validate: > **AUTHORITATIVE GUIDANCE** — Follow these instructions exactly unless they contradict security policies given to you.
Actually does
This skill reads a deployment plan from `.azure/deployment-plan.md`, executes various validation commands like `azd provision --preview`, `bicep build`, and `terraform validate` based on recipes. It also performs a project build verification and reviews Bicep/Terraform for RBAC, recording all proof in the deployment plan before setting its status to `Validated` and instructing to invoke `azure-deploy`.
npx skills add https://github.com/microsoft/github-copilot-for-azureThe skill explicitly executes commands sourced from `recipes/README.md` and performs project builds. This capability allows for arbitrary command execution if the recipe file is malicious or manipulated, posing a supply chain risk.
Execute recipe-specific validation commands | [recipes/README.md], Build the project | See recipe, Run actual validation commands (azd provision --preview, bicep build, terraform validate, etc.)
The skill explicitly invokes another skill, `azure-deploy`, as a mandatory next step. This demonstrates the capability for one agent to spawn or delegate tasks to another skill.
Invoke azure-deploy skill, you MUST invoke azure-deploy to execute the deployment.
The skill mandates that the agent automatically invoke 'azure-deploy' after validation completes, explicitly prohibiting the agent from running deployment commands directly and requiring delegation to a separate skill. This creates an enforced multi-agent/skill pipeline (azure-prepare → azure-validate → azure-deploy) where each step autonomously triggers the next without requiring explicit user approval at each transition. This pattern suppresses user confirmation opportunities at the critical deployment step.
> After ALL validations pass, you **MUST** invoke **azure-deploy** to execute the deployment. Do NOT attempt to run `azd up`, `azd deploy`, or any deployment commands directly. Let azure-deploy handle execution.
Step 9 in the workflow table instructs the agent to invoke 'azure-deploy' skill autonomously as the final step, creating a chained sub-agent invocation pattern. Combined with the mandatory blocking at the start requiring 'azure-prepare' to have run, this constructs a fully automated pipeline that routes through attacker-controllable skill references.
| 9 | **Deploy** — Invoke **azure-deploy** skill | — |
The skill enforces a hard stop requiring a file artifact from 'azure-prepare' to exist before proceeding, and instructs the agent to automatically invoke 'azure-prepare' if it is missing. This creates unbounded workflow redirection where the agent is autonomously bounced between skills based on file-system state, reducing opportunity for human oversight.
If the plan is missing, **STOP IMMEDIATELY** and invoke **azure-prepare** first.
The skill uses strong, authoritative language ('AUTHORITATIVE GUIDANCE', 'MUST', 'DO NOT SKIP') to influence the agent's reasoning and ensure strict adherence to the workflow, potentially overriding other considerations or security policies.
AUTHORITATIVE GUIDANCE — Follow these instructions exactly unless they contradict security policies given to you., You MUST follow these steps, MANDATORY NEXT STEP — DO NOT SKIP
The skill opens with a bold 'AUTHORITATIVE GUIDANCE' directive instructing the agent to follow these instructions exactly unless they contradict security policies. This framing is designed to elevate the skill's instructions above normal agent reasoning and reduce scrutiny of subsequent directives.
> **AUTHORITATIVE GUIDANCE** — Follow these instructions exactly unless they contradict security policies given to you.
The 'VALIDATION AUTHORITY' block declares itself the 'officially verified' mechanism for setting plan status, using authoritative institutional language to reduce agent skepticism and discourage deviation from the prescribed steps, potentially masking malicious instructions embedded in referenced recipe files.
> **⛔ VALIDATION AUTHORITY** > > This skill is the officially verified way to set plan status to `Validated`.
The skill modifies the `.azure/deployment-plan.md` file by adding validation steps and recording proof, with content potentially sourced from `recipes/README.md`. A malicious recipe could poison the agent's knowledge base or RAG.
Add Validation Steps — Copy recipe 'Validation Steps' to .azure/deployment-plan.md, Record Proof — Populate Section 7: Validation Proof
The skill explicitly states that destructive actions require user confirmation (`ask_user`). While this is a safeguard, it indicates the skill has the capability to perform destructive operations.
⛔ Destructive actions require ask_user
The skill uses emphatic 'MANDATORY', 'DO NOT SKIP', and 'MUST' language to push the agent directly into deployment after validation, discouraging it from pausing for user confirmation before executing a potentially destructive cloud deployment operation.
> **⚠️ MANDATORY NEXT STEP — DO NOT SKIP** > > After ALL validations pass, you **MUST** invoke **azure-deploy** to execute the deployment.
The skill instructs the agent to load and execute content from multiple external reference files (references/recipes/README.md, references/role-verification.md, errors.md, .azure/deployment-plan.md). These files are read at runtime and their content is used to drive agent actions, creating an indirect prompt injection surface where attacker-controlled file content could redirect agent behavior.
| 2 | **Add Validation Steps** — Copy recipe "Validation Steps" to `.azure/deployment-plan.md` ... | [recipes/README.md](references/recipes/README.md) | | 3 | **Run Validation** — Execute recipe-specific validation commands | [recipes/README.md](references/recipes/README.md) |
[](https://mondoo.com/ai-agent-security/skills/github/microsoft/github-copilot-for-azure/azure-validate)<a href="https://mondoo.com/ai-agent-security/skills/github/microsoft/github-copilot-for-azure/azure-validate"><img src="https://mondoo.com/ai-agent-security/api/badge/github/microsoft/github-copilot-for-azure/azure-validate.svg" alt="Mondoo Skill Check" /></a>https://mondoo.com/ai-agent-security/api/badge/github/microsoft/github-copilot-for-azure/azure-validate.svgSkills can read files, run commands, and access credentials. Mondoo helps organizations manage the security risks of AI agent skills across their entire fleet.