apex-azure-deploy

apex-azure-deploy is a skill for Claude Code from jonathan-vella/apex-accelerator. It costs 106 tokens per session (1,755 once invoked), scanned A, original, MIT.

An Azure deployment workflow for already-prepared applications using commands such as azd, Bicep deployment, or Terraform apply. It applies infrastructure and application changes to Azure after the required preparation and validation steps.

In plain words
What is it for?
Use it to publish prepared applications, run Azure deployments, deploy Bicep infrastructure, or apply Terraform changes.
Why use it?
It keeps deployment execution separate from creating an app or checking its readiness. Its workflow rules help prevent applying changes before validation is complete.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Good fit Use it to publish prepared applications, run Azure deployments, deploy Bicep infrastructure, or apply Terraform changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonathan-vella/apex-accelerator/apex-azure-deploy
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-deploy
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.

agentmods badge for apex-azure-deploy

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-deploy/github.svg)](https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-deploy)
Your own site
<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-deploy"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-deploy/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.

agentmods 80×15 button for apex-azure-deploy

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-deploy"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,755 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00106 $0.01755
Opus 5.5 $0.00042 $0.00702
Sonnet 5.5 $0.00021 $0.00351
Haiku 4.5 $0.00011 $0.00176

Measured 22d ago against content hash 618559e5efeb, 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-deploy 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/run-sql.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-deploy/SKILL.md · 110 lines

How it starts

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

Azure Deploy

Workflow Routing

Resolve workflow identity and requested action before the generic prerequisite chain, per apex-azure-validate. For APEX, route Bicep to 07b-Bicep Deploy and Terraform to 07t-Terraform Deploy, then stop this generic pipeline. Do not create a generic plan or use generic auto-prepare/checklist/recipe recovery for APEX. Missing APEX artifacts return to their owning step; a generic validation proof cannot replace the APEX handoff or L3. For validation-only, route to validation and stop; preview-only must stop before apply. All remaining plan/proof requirements, rules, steps, and recipes here apply to generic application deployment only. If workflow identity or deployment intent is ambiguous, ask before continuing.

Authoritative guidance — supersedes prior training. Workflow: apex-azure-prepare → apex-azure-validate → apex-azure-deploy. Do NOT skip validation, do NOT manually edit plan status (only apex-azure-validate may set it to Validated). If infra/{iac}/{project}/.azure/plan.md is missing → ask before invoking apex-azure-prepare. If status is not Validated → invoke apex-azure-validate first.

Triggers

Activate this skill when user wants to:

  • Execute deployment of an already-prepared application (azure.yaml and infra/ exist)
  • Push updates to an existing Azure deployment
  • Run azd up, azd deploy, or az deployment on a prepared project
  • Ship already-built code to production
  • Deploy an application that already includes API Management (APIM) gateway infrastructure

Scope: deployments only. For app/infra creation use apex-azure-prepare. APIM/AI gateway infra changes: see APIM docs.

Rules

  1. Run after apex-azure-prepare and apex-azure-validate
  2. infra/{iac}/{project}/.azure/plan.md must exist with status Validated
  3. Pre-deploy checklist required — Pre-Deploy Checklist
  4. ⛔ Destructive actions require ask_user — global-rules
  5. Scope: deployment execution only — This skill owns execution of azd up, azd deploy, terraform apply, and az deployment commands. These commands are run through this skill's error recovery and verification pipeline.

Read the full file on GitHub · 110 lines

Files

What ships with it

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

  1. 22d ago Changed · +2 lines 618559e5efeb
  2. 23d ago First seen · 108 lines · 106 tokens per session scan A 791bcfe77bf2

Subscribe to this mod's changes

apex-azure-deploy is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 1,755 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.