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.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)<a href="https://agentmods.dev/instructions/azure-samples/apim-unified-ai-gateway-sample/terraform"><img src="https://agentmods.dev/badge/instructions/azure-samples/apim-unified-ai-gateway-sample/terraform/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"><img src="https://agentmods.dev/badge/instructions/azure-samples/apim-unified-ai-gateway-sample/terraform.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.01387 | $0.01387 |
| Opus 5 | $0.00694 | $0.00694 |
| Sonnet 5 | $0.00277 | $0.00277 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
APIM-Unified-AI-Gateway-Sample terraform.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 10d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform Conventions
General Instructions
- Use Terraform to provision and manage infrastructure.
- Use version control for your Terraform configurations.
- Preserve file and folder casing: Never change file or folder name casing without explicit user approval. Path references are case-sensitive on Linux but not on Windows, so changing casing can break deployments (e.g., policy fragment paths, module source paths). Always verify path references match exactly after any file operations.
Security
- Always use the latest stable version of Terraform and its providers.
- Regularly update your Terraform configurations to incorporate security patches and improvements.
- Store sensitive information in a secure manner, such as using Azure Key Vault.
- Regularly rotate credentials and secrets.
- Automate the rotation of secrets, where possible.
- Use environment variables to reference values stored in secure vaults.
- This keeps sensitive values out of your Terraform state files.
- Never commit sensitive information such as credentials, API keys, passwords, certificates, or Terraform state to version control.
- Use
.gitignoreto exclude files containing sensitive information from version control.
- Use
- Always mark sensitive variables as
sensitive = truein your Terraform configurations.- This prevents sensitive values from being displayed in the Terraform plan or apply output.
- Use role-based access control (RBAC) to control access to resources.
- Follow the principle of least privilege when assigning permissions.
- Use network security groups and firewalls to control network access to resources.
- Deploy resources in private networks whenever possible.
- Use public endpoints only for resources that require direct internet access.
- Use encryption for sensitive data at rest and in transit.
- Enable encryption for storage accounts, databases, and other data stores.
- Use TLS for communication between services.
- Regularly review and audit your Terraform configurations for security vulnerabilities.
- Use tools like
trivy,tfsec, orcheckovto scan your Terraform configurations for security issues.
- Use tools like
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.
- 10d ago First seen · 114 lines · 1,387 tokens per session scan A 8b4652fb6b90
APIM-Unified-AI-Gateway-Sample terraform.instructions.md is an instructions file published in the GitHub repository Azure-Samples/APIM-Unified-AI-Gateway-Sample (14 stars, last pushed 5mo ago), licensed MIT. It adds 1,387 tokens to every session, about $0.0069 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.
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).
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).
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.