agentmods.dev

azure-sql-database-container AGENTS.md

Repository instructions for AI coding agents working on Microsoft's Azure SQL Database container project. The file explains the project, its folders, and rules for keeping its documentation and skills consistent.

In plain words
What is it for?
Guide agents while editing the project, finding the right files, following repository conventions, and keeping facts about the local Azure SQL engine consistent.
Why use it?
Contributors need shared rules so changes to the repository do not contradict its other documentation or installable skills. It also clarifies that these instructions are for contributing to the project, not for using the container in another app.

Instructions file for CodexOpenCode

15 2d ago A scan 666 tokens original MIT
View the source file microsoft/azure-sql-database-container
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/microsoft/azure-sql-database-container/agents-md
Clone the repo
git clone --depth 1 https://github.com/microsoft/azure-sql-database-container

Made for: Codex, OpenCode.

Per session 666 This file is loaded in full into every session.
When invoked 666 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00666 $0.00666
Opus 5 $0.00333 $0.00333
Sonnet 5 $0.00133 $0.00133
Haiku 4.5 $0.00067 $0.00067

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

Security

Grade A, and why

azure-sql-database-container 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 2d 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.

AGENTS.md · 29 lines

How it starts

The opening of the file, as written. The whole thing — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Guidance for AI coding agents working in this repository (the Azure SQL Database container Private Preview). If you instead want your own agent to run and build against the container in your project, install the skill: npx skills add microsoft/azure-sql-database-container. This file is about contributing to the repo, not about using the container.

What this project is

The Azure SQL Database container is the Azure SQL Database engine, running locally for development and CI. It is wire-compatible with Azure SQL Database in the Microsoft Azure cloud: same drivers, same T-SQL, same migrations, so deploying to the cloud is a connection-string change, not a code change. This repository ships the documentation site, the installable agent skills, and the copy-and-run build prompts; the engine image itself lives in a private preview registry.

Repository layout

  • skills/: the installable agent skill collection (npx skills add microsoft/azure-sql-database-container). This is the single source of truth for how an agent runs and builds against the container. Do not duplicate that how-to elsewhere; link to it.
  • docs/: the GitHub Pages site (what-is-the-container, prerequisites, getting-started, known-limitations, goals-of-the-private-preview, feedback-and-how-to-engage), plus docs/prompts/ (the build prompts) and docs/llms.txt.
  • README.md, SECURITY.md, CODE_OF_CONDUCT.md, LICENSE, and .github/ (issue and discussion templates).

Facts to keep consistent across docs and skills

These drift easily; keep them aligned everywhere when you edit:

  • x64 only. The image is x64 (linux/amd64). Do not present a non-x64 host as a supported platform, and do not use runtime brand names (Apple Container, Rosetta, Docker Desktop). The only platform note is: "on a non-x64 host, add --platform linux/amd64."
  • The engine does not auto-create databases. Provision appdb on a master connection before connecting to it. In a user-database session USE returns Msg 40508 (Azure-faithful); a master connection is a provisioning session where USE is not blocked. Select the database in the connection string and develop in the user database.
  • Registry / image: sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io/azure-sql/db-dev:latest. Registry, tag, and credentials are provisional during Private Preview.
  • Do not advertise things that do not exist (no empty sample folders, no unbuilt skill collections).
  • Feedback links: bug reports go to https://aka.ms/azuresqldb-container-bug, feature requests to https://aka.ms/azuresqldb-container-feature-request.

Read the full file on GitHub · 29 lines

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. 2d ago First seen · 29 lines · 666 tokens per session scan A fc71bfeb506b

Subscribe to this mod's changes

azure-sql-database-container AGENTS.md is an instructions file published in the GitHub repository microsoft/azure-sql-database-container (15 stars, last pushed 2d ago), licensed MIT. It adds 666 tokens to every session, about $0.0033 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.

DatabasesDevOps and cloudWriting and docs
Related

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.

openai/codex · 5,182 tokens

buildNext

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

next.js 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

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

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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,345 tokens