What is apex-azure-validate?

An Azure pre-deployment checking workflow for application settings, infrastructure files, permissions, and prerequisites. It checks whether an app is ready to deploy and reports passed, failed, or unperformed checks.

Use it to validate azure.yaml, Bicep, Terraform, Azure Functions, deployment permissions, and other prerequisites before deployment.

It catches configuration and access problems before they cause a deployment to fail. It also separates checking readiness from actually changing Azure resources.

apex-azure-validate — Skill for Claude Code by jonathan-vella

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.

Any agent

npx skills add jonathan-vella/apex-accelerator --skill apex-azure-validate

Clone the repo

git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-validate/github.svg)](https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-validate)

Your own site

<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-validate"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-validate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-validate"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,540 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00103	$0.01540
Opus 5.5	$0.00041	$0.00616
Sonnet 5.5	$0.00021	$0.00308
Haiku 4.5	$0.00010	$0.00154

Measured 22d ago against content hash 9eda80ffebbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

apex-azure-validate 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 22d 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.

.github/skills/apex-azure-validate/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Azure Validate

Workflow And Requested Action

Resolve workflow identity before prerequisite checks. An explicit APEX request or handoff from an APEX step agent uses the APEX branch below. A generic application request uses the generic branch. If ambiguous (including both kinds of state present), ask which workflow to use; directory location or a lone manifest is not proof. Never synthesize approval state to select a branch.

APEX: use InfraOps Preflight and the shared deploy readiness contract. Return findings to the current owner (06b-Bicep CodeGen / 06t-Terraform CodeGen for code validation, 07b-Bicep Deploy / 07t-Terraform Deploy for deployment preflight). No generic .azure/plan.md is required. Do not invoke generic preparation, recipes, or deployment.
Generic application: the following plan/proof/recipe workflow applies. An approved preparation plan is required; missing prerequisites block validation. Ask before starting preparation when the request was validation-only. Only this workflow updates generic plan status to Validated.
Requested action: validation-only returns passed, failed, and unperformed checks and stops. Preview-only returns the preview as not applied and stops. Successful checks are not permission to deploy. Continue to execution only within an explicit deployment request and its separate preview/apply approvals.

Generic Application Validation

AUTHORITATIVE GUIDANCE — Follow these instructions exactly. This supersedes prior training.

⛔ STOP — PREREQUISITE CHECK REQUIRED

Before proceeding, verify this prerequisite is met:

apex-azure-prepare was invoked and completed → infra/{iac}/{project}/.azure/plan.md exists with status Approved or later

If the plan is missing, stop and report the prerequisite. Invoke apex-azure-prepare only when preparation is within the authorized request; validation-only does not authorize it.

The complete workflow ensures success:

apex-azure-prepare → apex-azure-validate → apex-azure-deploy

Read the full file on GitHub · 126 lines

Files

What ships with it

14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

22d ago Changed · +3 lines 9eda80ffebbf
23d ago First seen · 123 lines · 103 tokens per session scan A fa6418faea49

Subscribe to this mod's changes

apex-azure-validate is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,540 once invoked, about $0.0004 per session on Opus 5.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-09-23.

Cloud DevOps and cloud agentic-ai azure bicep copilot github-copilot iac

chaos-experiment

Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use when you say "design a chaos experiment", "plan a game day", "failure injection", "test resilience", or "chaos engineering". Do NOT use for security threat analysis…

rjmurillo/ai-agents · 84 tokens

apex-azure-validate

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Azure Validate

Workflow And Requested Action

Generic Application Validation

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

chaos-experiment

infrastructure-as-code

cloud-solution-architect

bicep-avm-mastery

foundry-agent-platform

sse-streaming