Borrowing it
Nothing to install: this file belongs to Azure-Samples/AzureML_industry_labs. 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/AzureML_industry_labs/main/AGENTS.mdgit clone --depth 1 https://github.com/Azure-Samples/AzureML_industry_labsWrote 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/azureml_industry_labs/agents-md)<a href="https://agentmods.dev/instructions/azure-samples/azureml_industry_labs/agents-md"><img src="https://agentmods.dev/badge/instructions/azure-samples/azureml_industry_labs/agents-md.svg" alt="Measured on agentmods" 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.02921 | $0.02921 |
| Opus 5 | $0.01460 | $0.01460 |
| Sonnet 5 | $0.00584 | $0.00584 |
| Haiku 4.5 | $0.00292 | $0.00292 |
Grade A, and why
AzureML_industry_labs AGENTS.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 7d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This document describes the workspace structure, conventions, and patterns for AI coding agents working in the Azure ML Industry Labs repository. Use this as context when generating, modifying, or reviewing labs.
Overview
Azure ML Industry Labs (azureml_industry_labs) is a collection of end-to-end machine learning labs across different industry use-cases, built on Azure Machine Learning. Each lab demonstrates a complete MLOps workflow — data preprocessing, model training, model registration, and deployment — using the Azure ML SDK v2, MLflow experiment tracking, and managed endpoints.
Labs are self-contained Python projects (not notebooks) with a shared structural convention.
Directory Structure
Root
azureml_industry_labs/
├── README.md # Repo overview, labs table, quick start
├── CONTRIBUTING.md # Guidelines for adding new labs
├── AGENTS.md # This file — workspace context for AI agents
├── LICENSE # MIT License
├── images/ # Shared images and diagrams
│
└── <lab_name>/ # Each lab is a top-level directory
Lab Structure (Standard Template)
Every lab must follow this structure. When creating a new lab, replicate this layout exactly:
<lab_name>/
├── main.py # Pipeline orchestration & job submission
├── lab.json # Lab metadata (used by CI to update root README)
├── requirements.txt # Python dependencies (pinned versions)
├── Dockerfile # Custom Azure ML environment image
├── README.md # Lab-specific documentation
├── .amlignore # Files to exclude from Azure ML snapshots
├── .gitignore # Files to exclude from version control
├── data_processing/
│ ├── __init__.py
│ └── preprocess.py # Reusable dataset class (PyTorch Dataset)
├── model/
│ ├── __init__.py
│ └── <model_name>.py # Model architecture definition
└── pipeline/
├── preprocess_step.py # Data preprocessing pipeline step
├── train_step.py # Model training pipeline step
├── register_model.py # Model registration pipeline step
├── deploy_endpoint.py # Endpoint deployment pipeline step
└── score.py # Scoring script for batch/online inference
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.
- 7d ago First seen · 262 lines · 2,921 tokens per session scan A b2c6907a2a6f
AzureML_industry_labs AGENTS.md is an instructions file published in the GitHub repository Azure-Samples/AzureML_industry_labs (5 stars, last pushed 1mo ago), licensed MIT. It adds 2,921 tokens to every session, about $0.0146 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-31.
Other instructions, from other repositories
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).
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.
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 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).
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.