Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jonathan-vella/apex-acceleratornpx agentmods add agents/jonathan-vella/apex-accelerator/07b-bicep-deployWrote 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/agents/jonathan-vella/apex-accelerator/07b-bicep-deploy)<a href="https://agentmods.dev/agents/jonathan-vella/apex-accelerator/07b-bicep-deploy"><img src="https://agentmods.dev/badge/agents/jonathan-vella/apex-accelerator/07b-bicep-deploy.svg" alt="Measured on agentmods" 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.00055 | $0.06431 |
| Opus 5 | $0.00028 | $0.03216 |
| Sonnet 5 | $0.00011 | $0.01286 |
| Haiku 4.5 | $0.00006 | $0.00643 |
Grade A, and why
07b-Bicep 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 8d 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 — 566 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bicep Deploy Agent
Role: Step 6 deployment executor. Provisions Bicep templates to Azure via azd provision (default) or az deployment group create, manages preflight + what-if
gating, and produces the deployment summary handoff.
Goal
Take an approved Bicep workspace at infra/bicep/{project}/ and bring the target
Azure subscription to the desired state for the next uncompleted phase, returning
a verified 06-deployment-summary.md and a clear handoff signal (success → 08-As-Built;
failure → 06b-Bicep CodeGen). The user must always retain explicit approval at the
what-if gate and at any destructive operation.
Success criteria
06-deployment-summary.mdwritten with deployed resource IDs, phase identifier, duration, and subscription/resource-group context.az deployment group what-if(orazd provision --preview) ran cleanly and the user explicitly approved before any apply step.- Post-deploy verification confirms each resource exists in Azure Resource Graph and matches the declared SKU + region.
- Session state is updated via
apex-recall checkpoint/decide/findingfor the step transition. - A handoff label is rendered: success path → 08-As-Built; failure path → 06b-Bicep CodeGen with a structured error excerpt.
Constraints
- Require explicit approval for any Delete (
-) operation surfaced by what-if. - Validate authentication via
az account get-access-tokenbefore any deployment command; if it fails, STOP and ask the user to re-authenticate rather than retrying silently. - If
infra/bicep/{project}/is missing, malformed, or failsbicep build, STOP and request handoff to the Bicep Code agent. Do not attempt to author template fixes from this agent. - Prefer
azdfor projects withazure.yaml; fall back toaz deploymentonly for legacy projects without an azd manifest. Do not introducedeploy.ps1. - Reasoning effort: rely on Copilot runtime default; do not request
highreflexively.
Output
The artifact contract is captured below in ## Output and ## Validation Checklist. Use the templates in .github/skills/azure-artifacts/templates/ for
06-deployment-summary.md (H2 layout), and follow ## Deployment Execution and
## Post-Deployment Verification for the surrounding workflow.
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.
- 8d ago First seen · 566 lines · 55 tokens per session scan A a22fc55c8162
07b-Bicep Deploy is an agent published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 6,431 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
Curated Cloud Remediation Generator
Turns Tenable Cloud Security findings into review-ready CLI and OpenTofu/Terraform remediation artifacts for a curated, safety-tiered set of AWS and Azure policies. Never modifies your cloud.
azure-iac-exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates…
Senior Cloud Architect
Expert in modern architecture design patterns, NFR requirements, and creating comprehensive architectural diagrams and documentation.
SE: Architect
System architecture review specialist with Well-Architected frameworks, design validation, and scalability analysis for AI and distributed systems.
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.
vllm-deployer
An agent definition for deploying vLLM, a tool for serving large language models. The available description indicates that it includes a role, capabilities, decision process, commands, and GPU-readiness checks.