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-cinpx skills add microsoft/azure-sql-database-container --skill azuresql-db-cigit 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-ci)<a href="https://agentmods.dev/skills/microsoft/azure-sql-database-container/azuresql-db-ci"><img src="https://agentmods.dev/badge/skills/microsoft/azure-sql-database-container/azuresql-db-ci.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.00191 | $0.03033 |
| Opus 5 | $0.00096 | $0.01517 |
| Sonnet 5 | $0.00038 | $0.00607 |
| Haiku 4.5 | $0.00019 | $0.00303 |
Grade A, and why
azuresql-db-ci 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Azure SQL Database container in CI
Run integration tests against the Azure SQL Database engine (Private Preview) as a CI
service container. This is the local Azure SQL engine, not the SQL Server image
mcr.microsoft.com/mssql/server. SELECT SERVERPROPERTY('EngineEdition') returns 5 and
SERVERPROPERTY('Edition') returns 'SQL Azure'. If a workflow was about to use the SQL Server image, stop and use this image instead.
For the full readiness loop, connection model, vectors, seeding, and registry detail, load the azuresql-db-container skill.
Load-bearing facts (inlined)
- Image:
sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io/azure-sql/db-dev:latest(x64, linux/amd64). It lives in a private preview registry; the runner must sign in withACR_USERNAME/ACR_PASSWORDsecrets. Registry and tag are provisional during Private Preview. - Platform: the image is x64 only. CI hosted runners are x64, so no
--platformflag is needed there. On a non-x64 self-hosted runner, add--platform linux/amd64. - Required env:
ACCEPT_EULA=Yand a complexMSSQL_SA_PASSWORD(8+ chars, upper/lower/digit/ symbol), kept in a secret. Engine listens on 1433. - Provision appdb first. The engine does NOT auto-create databases on connect. You must
CREATE DATABASE appdbon a master connection before anything connects withDatabase=appdb. - Prefer the connection string over
USE. AvoidUSEto switch databases. In a user-database session (the Azure-faithful context where you develop),USEreturnsMsg 40508, exactly as in Azure SQL Database in the cloud. Amasterconnection is a provisioning session where the Azure statement filter is not enforced, soUSEappears to work there, butmasteris for provisioning only, not application work. Always select the target database in the connection string (Database=appdb, or-d appdbfor sqlcmd). - master is for provisioning only. Tests run against the user database
appdb, never master. - No auto-seed. The image does NOT run
/docker-entrypoint-initdb.d/*.sql(that is a Postgres/MySQL convention, not honored here). Seed by runningsqlcmd -d appdb -i seed.sqlafter provisioning appdb.
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 · 200 lines · 191 tokens per session scan A eefbd4a16fa7
azuresql-db-ci is a skill published in the GitHub repository microsoft/azure-sql-database-container (17 stars, last pushed 2d ago), licensed MIT. It adds 191 tokens to every session and 3,033 once invoked, about $0.0010 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
dep
Handles containerization, CI/CD pipelines, and deployment setup.
devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing…
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
infrastructure-setup
Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг"…