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.
npx agentmods add skills/microsoft/azure-sql-database-container/azuresql-db-schema-migrationnpx skills add microsoft/azure-sql-database-container --skill azuresql-db-schema-migrationgit clone --depth 1 https://github.com/microsoft/azure-sql-database-containerWrote 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/skills/microsoft/azure-sql-database-container/azuresql-db-schema-migration)<a href="https://agentmods.dev/skills/microsoft/azure-sql-database-container/azuresql-db-schema-migration"><img src="https://agentmods.dev/badge/skills/microsoft/azure-sql-database-container/azuresql-db-schema-migration.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 | $0.00151 | $0.02506 |
| Opus 5 | $0.00076 | $0.01253 |
| Sonnet 5 | $0.00030 | $0.00501 |
| Haiku 4.5 | $0.00015 | $0.00251 |
Grade A, and why
azuresql-db-schema-migration 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 4d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema migrations on the Azure SQL Database container
Apply schema migrations to the local Azure SQL Database container the same way
you would against the cloud, so dev and prod stay identical. This is the Azure SQL
Database engine (SELECT SERVERPROPERTY('EngineEdition') returns 5,
Edition returns 'SQL Azure'), not the SQL Server image
mcr.microsoft.com/mssql/server. If a tool or template points at the SQL Server image,
stop and use the image below instead.
The one rule that breaks every migration tool
The engine does NOT auto-create databases on connect. Every migration tool assumes the target database already exists. So:
- Provision
appdbon a master connection FIRST. - Then point the migration tool at the user database (
Database=appdb).
Avoid USE to switch databases. In a user-database session (the
Azure-faithful context where you develop), USE returns Msg 40508, exactly as in
Azure SQL Database in the cloud. A master connection is a provisioning provisioning
session where the Azure statement filter is not enforced, so USE appears to
work there, but master is for provisioning only, not
application work. Always select the target database in the connection string
(Database=appdb, or -d appdb for sqlcmd). A master connection is for
provisioning only; run migrations against appdb.
Start the container and provision appdb (canonical recipe)
The engine is not ready the instant docker run returns. Wait with a retry loop
and create appdb inside that same loop. Image is x64 only; on a non-x64 host the
recipe adds --platform linux/amd64 automatically. The registry is private during
Private Preview, so sign in first.
docker login sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io # pull-only creds by signing up at https://aka.ms/sqldbcontainerpreview-signup
# Pick a free host port and add the platform flag only on a non-x64 host (works in bash and zsh).
HOST_PORT=1433; while lsof -nP -iTCP:"$HOST_PORT" -sTCP:LISTEN >/dev/null 2>&1; do HOST_PORT=$((HOST_PORT+1)); done
PLATFORM=(); case "$(docker info -f '{{.Architecture}}' 2>/dev/null)" in x86_64|amd64) ;; *) PLATFORM=(--platform linux/amd64);; esac
docker rm -f sqldb 2>/dev/null
docker run -d --name sqldb "${PLATFORM[@]}" -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=YourStr0ng_Passw0rd" \
-p "$HOST_PORT:1433" sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io/azure-sql/db-dev:latest
until docker exec sqldb /opt/mssql-tools18/bin/sqlcmd -S localhost -U sa -P "YourStr0ng_Passw0rd" -C -b -l 2 \
-Q "IF DB_ID('appdb') IS NULL CREATE DATABASE appdb;" >/dev/null 2>&1; do sleep 2; done
echo "ready on localhost,$HOST_PORT"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 183 lines · 151 tokens per session scan A ee522e0da997
azuresql-db-schema-migration is a skill published in the GitHub repository microsoft/azure-sql-database-container (17 stars, last pushed 2d ago), licensed MIT. It adds 151 tokens to every session and 2,506 once invoked, about $0.0008 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 skills, from other repositories
haven-setup
Bring up the LangWatch dev stack via thuishaven (make haven up) — one-time proxy/CA setup, reusing existing local ClickHouse/Postgres/Redis, WSL2/no-colima fallback for langyagent, and the known gotchas that silently break it.
qdrant-deployment-options
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.
deploy-registry-server-with-cnpg
Deploy the ToolHive Registry Server to a Kind cluster with CloudNativePG (CNPG) PostgreSQL database. Use when you need a production-like PostgreSQL setup with the CNPG operator.
n8n-azure
Application-specific configuration for deploying n8n to Azure Container Apps with PostgreSQL. Infrastructure should be generated fresh by the azure-prepare → azure-validate → azure-deploy pipeline.
oracle-aidb-docker-setup
Bring up Oracle 26ai Free in Docker, create a project-scoped app user with USERS tablespace + ONNX-friendly grants, and write a .env ready for the rest of the build-paths skills. Idempotent — safe to re-invoke. Use when any project needs a fresh local Oracle 26ai instance.
cnpg
Create and operate CloudNativePG (CNPG) Postgres databases on Kubernetes the GitOps/Flux way - on managed cloud (GKE + GCS via Workload Identity) OR self-hosted (K3s/bare-metal + any S3-compatible store via a credentials secret). Covers Cluster + ScheduledBackup manifests, barman WAL archiving, pgvector, PITR…