azure-validate

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

An Azure deployment-readiness checker for application settings, infrastructure code, permissions, and required setup.

In plain words
What is it for?
Use it to check azure.yaml, Bicep, Terraform, and Azure Functions projects after planning and before deployment.
Why use it?
It catches configuration and infrastructure problems before deployment, reducing failed Azure releases and unclear deployment errors.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to check azure.yaml, Bicep, Terraform, and Azure Functions projects after planning and before deployment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonathan-vella/apex-accelerator/azure-validate
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 azure-validate
Clone the repo
git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

Made for: Claude Code, Codex.

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 azure-validate

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-validate.svg)](https://agentmods.dev/skills/jonathan-vella/apex-accelerator/azure-validate)
Your own site
<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/azure-validate"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-validate.svg" alt="Measured on agentmods" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,075 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 6 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 18
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 59
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 62
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 64
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • medium Prompt Injection · line 57
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 65
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
How audits are shown
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.00094 $0.01075
Opus 5 $0.00047 $0.00537
Sonnet 5 $0.00019 $0.00215
Haiku 4.5 $0.00009 $0.00108

Measured 4d ago against content hash 0f77ee35bc5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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 4d 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/azure-validate/SKILL.md · 98 lines

How it starts

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

Azure Validate

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

⛔ STOP — PREREQUISITE CHECK REQUIRED

Before proceeding, verify this prerequisite is met:

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

If the plan is missing, STOP IMMEDIATELY and invoke azure-prepare first.

The complete workflow ensures success:

azure-prepareazure-validateazure-deploy

Triggers

  • Check if app is ready to deploy
  • Validate azure.yaml or Bicep
  • Run preflight checks
  • Troubleshoot deployment errors

Rules

  1. Run after azure-prepare, before azure-deploy
  2. All checks must pass—do not deploy with failures
  3. Destructive actions require ask_userglobal-rules

Validation Commands (per recipe)

The per-recipe validation commands are bundled in references/recipes/. Common ones:

azd provision --preview                 # AZD recipes
bicep build infra/bicep/{project}/main.bicep && bicep lint infra/bicep/{project}/main.bicep
terraform fmt -check && terraform validate && npm run validate:terraform
npm run validate:iac-security-baseline  # cross-cutting baseline
npm run validate:all                    # full repo validator suite

Load the recipe-specific README to confirm the exact command set for the project's IaC tool.

Steps

# Action Reference
1 Load Plan — Read infra/{iac}/{project}/.azure/plan.md for recipe and configuration. If missing → run azure-prepare first infra/{iac}/{project}/.azure/plan.md
2 Run Validation — Execute recipe-specific validation commands recipes/README.md
3 Build Verification — Build the project and fix any errors before proceeding See recipe
4 Record Proof — Populate Section 7: Validation Proof with commands run and results infra/{iac}/{project}/.azure/plan.md
5 Resolve Errors — Fix failures before proceeding See recipe's errors.md
6 Update Status — Only after ALL checks pass, set status to Validated infra/{iac}/{project}/.azure/plan.md
7 Deploy — Invoke azure-deploy skill

Read the full file on GitHub · 98 lines

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. 4d ago First seen · 98 lines · 94 tokens per session scan A 0f77ee35bc5f

Subscribe to this mod's changes

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