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/azure-yaml.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/azure-yaml)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/azure-yaml"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/azure-yaml/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/azure-yaml"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/azure-yaml.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.00365 | $0.00365 |
| Opus 5.5 | $0.00146 | $0.00146 |
| Sonnet 5.5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
apex-accelerator azure-yaml.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 1mo 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.
What it actually says
azure.yaml Conventions
Rules for azure.yaml manifests in this multi-project repository.
Co-Location Pattern (Mandatory)
Each project is a self-contained azd project inside its IaC directory:
infra/{iac}/{project}/azure.yaml ← manifest lives here
infra/{iac}/{project}/.azure/ ← azd state (git-ignored)
Required Fields
infra.path: .— always relative to the manifest locationinfra.provider: biceporinfra.provider: terraform— must match the parent directory
Prohibited
- Never place
azure.yamlat the repository root — breaks multi-project isolation - Never use absolute paths or
../ininfra.path
Environment Naming
Use {project}-{env} pattern to avoid collisions across projects:
# Good: hub-spoke-dev, webapp-prod
# Bad: dev, production (ambiguous across projects)
Running azd
cd infra/{iac}/{project} && azd up # preferred
azd -C infra/{iac}/{project} up # alternative from repo root
Minimal Manifest
name: { project }
infra:
provider: bicep # or terraform, matching the parent directory
path: .
Track-specific azd details (authentication checks, environment commands, directory layout)
live in infra/bicep/AGENTS.md and infra/terraform/AGENTS.md.
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.
- 1mo ago Changed · -6 lines · +18 tokens per session 7331633789cf
- 1mo ago First seen · 62 lines · 347 tokens per session scan A a27945cdada7
apex-accelerator azure-yaml.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 365 tokens to every session, about $0.0015 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.