Borrowing it
Nothing to install: this file belongs to jonathan-vella/apex-accelerator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jonathan-vella/apex-accelerator/main/.github/instructions/iac-bicep-best-practices.instructions.mdgit 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/instructions/jonathan-vella/apex-accelerator/iac-bicep-best-practices)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/iac-bicep-best-practices"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/iac-bicep-best-practices/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/instructions/jonathan-vella/apex-accelerator/iac-bicep-best-practices"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/iac-bicep-best-practices.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.01031 | $0.01031 |
| Opus 5.5 | $0.00412 | $0.00412 |
| Sonnet 5.5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
apex-accelerator iac-bicep-best-practices.instructions.md 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 6d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bicep Best Practices
Azure values are canonical in Copilot instructions; shared naming, AVM, and security procedures live in apex-azure-defaults. This file covers Bicep-specific patterns. Discovered policy constraints always take precedence.
Policy and Security
Azure Policy always wins. Code adapts to policy, never the reverse.
Cross-reference 04-governance-constraints.json before writing templates; for Deny policies
prefer azurePropertyPath and fall back to bicepPropertyPath. Shared rules:
references/iac-security-baseline.md (security, networking, diagnostics) and
references/iac-policy-compliance.md (checklist, dynamic tags, Bicep translation).
Naming
| Resource | Max | Pattern | Example |
|---|---|---|---|
| Storage | 24 | st{project}{env}{suffix} |
stcontosodev7xk2 |
| Key Vault | 24 | kv-{project}-{env}-{suffix} |
kv-contoso-dev-abc123 |
| SQL Server | 63 | sql-{project}-{env}-{suffix} |
sql-contoso-dev-abc123 |
Use lowerCamelCase for parameters, variables, resources, modules.
Avoid symbols named resourceGroup, subscription, managementGroup, tenant, az or sys when those
functions/namespaces are used. Prefer role-specific names such as projectResourceGroup; rename all references
together. Scope-function shadowing is a source defect, not a missing-module error that can be deferred.
Unique Names
Generate uniqueSuffix once in main.bicep via uniqueString(resourceGroup().id).
Pass to all modules. Use take() for length-constrained resources.
AVM Modules
Use AVM modules (br/public:avm/res/{service}/{resource}:{version}) for all
resources where one exists. Raw Bicep only when no AVM exists and user approves.
Pin to the latest published stable version, resolved at plan time through MCR tags or
the mcp_bicep_list_avm_metadata MCP helper (procedure and stale-pin/freeze policy in
apex-azure-defaults). Never copy a version
from apex-azure-defaults/references/avm-modules.md — versions are intentionally stripped.
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.
- 6d ago Changed · +2 lines · +29 tokens per session 034262590922
- 1mo ago Changed · -20 lines · -141 tokens per session 5a9dfd610909
- 1mo ago Changed · +7 lines · +186 tokens per session dd5dce769982
- 1mo ago First seen · 102 lines · 957 tokens per session scan A fef0a9a052ed
apex-accelerator iac-bicep-best-practices.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 1,031 tokens to every session, about $0.0041 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.