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.
npx skills add jonathan-vella/apex-accelerator --skill apex-azure-deploygit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/skills/jonathan-vella/apex-accelerator/apex-azure-deploy)<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.
<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>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.00106 | $0.01755 |
| Opus 5.5 | $0.00042 | $0.00702 |
| Sonnet 5.5 | $0.00021 | $0.00351 |
| Haiku 4.5 | $0.00011 | $0.00176 |
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.
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.
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, oraz deploymenton 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
- Run after apex-azure-prepare and apex-azure-validate
infra/{iac}/{project}/.azure/plan.mdmust exist with statusValidated- Pre-deploy checklist required — Pre-Deploy Checklist
- ⛔ Destructive actions require
ask_user— global-rules - Scope: deployment execution only — This skill owns execution of
azd up,azd deploy,terraform apply, andaz deploymentcommands. These commands are run through this skill's error recovery and verification pipeline.
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.
- references/global-rules.md 1.2 KB
- references/live-role-verification.md 3.1 KB
- references/pre-deploy-checklist.md 10 KB
- references/recipes/azcli/errors.md 698 B
- references/recipes/azcli/README.md 1.9 KB
- references/recipes/azcli/verify.md 503 B
- references/recipes/azd/ef-migrations.md 4.3 KB
- references/recipes/azd/errors.md 9.6 KB
- references/recipes/azd/functions-deploy.md 3.9 KB
- references/recipes/azd/post-deployment.md 4.5 KB
- references/recipes/azd/README.md 3.6 KB
- references/recipes/azd/sql-entra-auth.md 3.5 KB
- references/recipes/azd/sql-managed-identity.md 4.0 KB
- references/recipes/azd/verify.md 2.6 KB
- references/recipes/bicep/errors.md 710 B
- references/recipes/bicep/README.md 2.8 KB
- references/recipes/bicep/verify.md 274 B
- references/recipes/cicd/errors.md 709 B
- references/recipes/cicd/examples/azdo-azd.yml 487 B
- references/recipes/cicd/examples/azdo-multistage.yml 830 B
- references/recipes/cicd/examples/github-azd.yml 778 B
- references/recipes/cicd/examples/github-bicep.yml 1.1 KB
- references/recipes/cicd/README.md 1.5 KB
- references/recipes/cicd/verify.md 313 B
- references/recipes/README.md 590 B
- references/recipes/terraform/errors.md 603 B
- references/recipes/terraform/README.md 2.1 KB
- references/recipes/terraform/verify.md 297 B
- references/region-availability.md 3.9 KB
- references/sdk/azd-deployment.md 1.4 KB
- references/sdk/azure-identity-dotnet.md 1.0 KB
- references/sdk/azure-identity-java.md 1.3 KB
- references/sdk/azure-identity-py.md 1.2 KB
- references/sdk/azure-identity-ts.md 1.2 KB
- references/troubleshooting.md 6.2 KB
- scripts/run-sql.sh 1.1 KB runs code
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 · +2 lines 618559e5efeb
- 23d ago First seen · 108 lines · 106 tokens per session scan A 791bcfe77bf2
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.
Other skills, from other repositories
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…
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
cloud-solution-architect
Design well-architected Azure cloud systems — 10 design principles, 6 architecture styles, 44 design patterns, technology choices, WAF pillars.
bicep-avm-mastery
Azure Verified Modules (AVM), Bicep best practices, and MCP-powered infrastructure as code for Azure.
foundry-agent-platform
Microsoft Foundry agent deployment, orchestration, and cloud-native AI service patterns.
sse-streaming
POST-based Server-Sent Events streaming for Azure Functions — HTTP streaming, chunked response parsing, reconnection.