apex-accelerator: Instructions file for GitHub Copilot

.github/instructions/azure-yaml.instructions.md

apex-accelerator azure-yaml.instructions.md is an instructions file for GitHub Copilot from jonathan-vella/apex-accelerator. It costs 347 tokens per session, scanned A, original, MIT.

A set of rules for Azure Developer CLI configuration files in repositories that contain several independent infrastructure projects.

In plain words
What is it for?
Use it when creating or checking azure.yaml files for Bicep or Terraform projects, their infrastructure paths, and their deployment environments.
Why use it?
It prevents ambiguous project locations and environment names that can cause projects to share state or be run from the wrong directory.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is jonathan-vella/apex-accelerator's own configuration. It tells GitHub Copilot how to work on apex-accelerator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything apex-accelerator configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jonathan-vella/apex-accelerator/main/.github/instructions/azure-yaml.instructions.md
Clone the repo
git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

Made for: GitHub Copilot.

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 apex-accelerator azure-yaml.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/azure-yaml/github.svg)](https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/azure-yaml)
Your own site
<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.

agentmods 80×15 button for apex-accelerator azure-yaml.instructions.md

Your own site · 80×15
<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>
Per session 347 This file is loaded in full into every session.
When invoked 347 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00347 $0.00347
Opus 5 $0.00173 $0.00173
Sonnet 5 $0.00069 $0.00069
Haiku 4.5 $0.00035 $0.00035

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

Security

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 9d 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/instructions/azure-yaml.instructions.md · 62 lines

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 location
  • infra.provider: bicep or infra.provider: terraform — must match the parent directory

Prohibited

  • Never place azure.yaml at the repository root — breaks multi-project isolation
  • Never use absolute paths or ../ in infra.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

Bicep Projects

name: { project }
infra:
  provider: bicep
  path: .

Terraform Projects

name: { project }
infra:
  provider: terraform
  path: .
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. 9d ago First seen · 62 lines · 347 tokens per session scan A a27945cdada7

Subscribe to this mod's changes

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 347 tokens to every session, about $0.0017 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.

Related

Other instructions, from other repositories

plan-forge landing-zone.instructions.md

Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.

srnichols/plan-forge · 2,228 tokens

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.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens