Borrowing it
Nothing to install: this file belongs to Azure-Samples/APIM-Unified-AI-Gateway-Sample. 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/Azure-Samples/APIM-Unified-AI-Gateway-Sample/main/.github/instructions/terraform-azure.instructions.mdgit clone --depth 1 https://github.com/Azure-Samples/APIM-Unified-AI-Gateway-SampleWrote 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/azure-samples/apim-unified-ai-gateway-sample/terraform-azure)<a href="https://agentmods.dev/instructions/azure-samples/apim-unified-ai-gateway-sample/terraform-azure"><img src="https://agentmods.dev/badge/instructions/azure-samples/apim-unified-ai-gateway-sample/terraform-azure/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/azure-samples/apim-unified-ai-gateway-sample/terraform-azure"><img src="https://agentmods.dev/badge/instructions/azure-samples/apim-unified-ai-gateway-sample/terraform-azure.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.02475 | $0.02475 |
| Opus 5 | $0.01238 | $0.01238 |
| Sonnet 5 | $0.00495 | $0.00495 |
| Haiku 4.5 | $0.00248 | $0.00248 |
Grade A, and why
APIM-Unified-AI-Gateway-Sample terraform-azure.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 12d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Terraform Best Practices
Integration and Self-Containment
This instruction set extends the universal DevOps Core Principles and Taming Copilot directives for Azure/Terraform scenarios. It assumes those foundational rules are loaded but includes summaries here for self-containment. If the general rules are not present, these summaries serve as defaults to maintain behavioral consistency.
Incorporated DevOps Core Principles (CALMS Framework)
- Culture: Foster collaborative, blameless culture with shared responsibility and continuous learning.
- Automation: Automate everything possible across the software delivery lifecycle to reduce manual effort and errors.
- Lean: Eliminate waste, maximize flow, and deliver value continuously by reducing batch sizes and bottlenecks.
- Measurement: Measure everything relevant (e.g., DORA metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery) to drive improvement.
- Sharing: Promote knowledge sharing, collaboration, and transparency across teams.
Incorporated Taming Copilot Directives (Behavioral Hierarchy)
- Primacy of User Directives: Direct user commands take highest priority.
- Factual Verification: Prioritize tools for current, factual answers over internal knowledge.
- Adherence to Philosophy: Follow minimalist, surgical approaches—code on request only, minimal necessary changes, direct and concise responses.
- Tool Usage: Use tools purposefully; declare intent before action; prefer parallel calls when possible.
These summaries ensure the mode functions independently while aligning with the broader chat mode context. For full details, reference the original DevOps Core Principles and Taming Copilot instructions.
Chat Mode Integration
When operating in chat mode with these instructions loaded:
- Treat this as a self-contained extension that incorporates summarized general rules for independent operation.
- Prioritize user directives over automated actions, especially for terraform commands beyond validate.
- Use implicit dependencies where possible and confirm before any terraform plan or apply operations.
- Maintain minimalist responses and surgical code changes, aligning with the incorporated Taming philosophy.
- Planning Files Awareness: Always check for planning files in the
.terraform-planning-files/folder (if present). Read and incorporate relevant details from these files into responses, especially for migration or implementation plans. If speckit or similar planning files exist in user-specified folders, prompt the user to confirm inclusion or read them explicitly.
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.
- 12d ago First seen · 238 lines · 2,475 tokens per session scan A c4d5b141c6df
APIM-Unified-AI-Gateway-Sample terraform-azure.instructions.md is an instructions file published in the GitHub repository Azure-Samples/APIM-Unified-AI-Gateway-Sample (14 stars, last pushed 2d ago), licensed MIT. It adds 2,475 tokens to every session, about $0.0124 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 instructions, from other repositories
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
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).
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.