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 iac-commongit 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/iac-common)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/iac-common"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/iac-common/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/iac-common"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/iac-common.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 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 41 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 56 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 58 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 59 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 Tool Misuse · line 65 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Prompt Injection · line 67 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 73 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
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.00084 | $0.01772 |
| Opus 5 | $0.00042 | $0.00886 |
| Sonnet 5 | $0.00017 | $0.00354 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
iac-common 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 5d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IaC Common Skill
Shared deployment patterns used by both Bicep and Terraform deploy agents (07b, 07t) and review subagents.
Preflight validation (CLI auth, governance mapping, stop rules, known issues) has moved to the azure-validate skill. See
azure-validate/references/infraops-preflight.md.
Rules
- Preflight first — always run
azure-validatebefore invoking any deploy strategy in this skill - azd by default — use
azd provision/azd upfor all new projects. The legacydeploy.ps1path is deprecated; full decision matrix inreferences/azd-vs-deploy-guide.md. - Phased deployment for high-risk changes — split into Foundation → Security → Data → Compute → Edge with user approval at each gate
- Circuit breaker — stop deployment automatically when policy violations, governance failures, or budget breaches are detected; surface to user before retrying
- Set environment values before
--no-prompt—AZURE_SUBSCRIPTION_ID,AZURE_RESOURCE_GROUP,AZURE_ENV_NAME,AZURE_LOCATIONmust all be present (azd env get-values) - Use
azd env new {project}-{env}to avoid environment-name collisions across projects - Out of scope: preflight (use
azure-validate); code generation (useazure-bicep-patternsorterraform-patterns)
Steps
Standard deploy flow used by 07b-Bicep Deploy and 07t-Terraform Deploy:
- Preflight — run
azure-validate(auth, governance, plan, what-if review) - Set environment —
azd env set AZURE_SUBSCRIPTION_ID/RESOURCE_GROUP/LOCATION+ verify viaazd env get-values - Preview —
azd provision --preview(Bicep) orterraform plan(Terraform); user reviews destructive operations - Approve gate — user explicitly approves the preview before any apply
- Apply —
azd provision/azd up(Bicep) orterraform apply(Terraform); for high-risk projects, deploy in phases (Foundation → Security → Data → Compute → Edge) - Circuit-break on failure — stop on policy/governance/budget violations; surface diagnostics to user
- Hand off to
08-As-Builtfor documentation
What ships with it
20 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/avm-module-index.md 6.7 KB
- references/avm-version-freeze-gate.md 4.7 KB
- references/azd-vs-deploy-guide.md 15 KB
- references/azure-resource-graph-primer.md 3.0 KB
- references/circuit-breaker.md 3.3 KB
- references/codegen-do-dont.md 4.5 KB
- references/codegen-file-order.md 6.8 KB
- references/codegen-shared-workflow.md 10 KB
- references/contract-emission-and-handoff.md 4.9 KB
- references/deploy-shared-workflow.md 7.6 KB
- references/deploy-validation-checklist.md 6.6 KB
- references/deployment-strategies.md 4.2 KB
- references/governance-drift-routing.md 7.1 KB
- references/iac-planner-approval-gate.md 3.5 KB
- references/known-deploy-issues.md 12 KB
- references/placeholder-scan-protocol.md 668 B
- references/plan-consistency-checks.md 7.0 KB
- references/policy-precheck-contract.md 14 KB
- references/preflight-policy-checks.md 2.8 KB
- references/step4-required-artifacts.md 3.4 KB
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.
- 5d ago First seen · 112 lines · 84 tokens per session scan A 326dcef25955
iac-common is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,772 once invoked, about $0.0004 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.
Other skills, from other repositories
azure-deployment-operations
Production deployment patterns for Azure Static Web Apps, Container Apps, App Service, and infrastructure.
terraform-iac
Terraform and OpenTofu infrastructure as code best practices - generate HCL configurations, module patterns, state management, CI/CD workflows, and cloud provider templates for AWS, GCP, Azure.
nw-par-critique-dimensions
Platform design review critique dimensions and severity levels. Load when reviewing CI/CD pipelines, infrastructure, deployment strategies, observability, or security designs.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
ops-cost-optimization
Audits SaaS/PaaS, cloud commitment, and AI/LLM costs across Vercel, Supabase, AWS, and Cloudflare. Use when analyzing bills, right-sizing plans, or buying commitments.
render
Use when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire…