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/azure/documentdb-agent-kit/local-deploymentnpx skills add Azure/documentdb-agent-kit --skill local-deploymentgit clone --depth 1 https://github.com/Azure/documentdb-agent-kitWhat 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.00111 | $0.00523 |
| Opus 5 | $0.00056 | $0.00262 |
| Sonnet 5 | $0.00022 | $0.00105 |
| Haiku 4.5 | $0.00011 | $0.00052 |
Grade A, and why
documentdb-local-deployment 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.
What it actually says
Local Deployment & Developer Workflow — Azure DocumentDB
Image choices:
- Gateway (
ghcr.io/microsoft/documentdb/documentdb-local:latest) — MongoDB wire protocol on port 10260. Use this for app development. - psql-only (
mcr.microsoft.com/cosmosdb/ubuntu/documentdb-oss:...) — raw PostgreSQL on port 9712. Use only for direct SQL inspection.
Rules
- local-choose-deployment-method — Pick the simplest local option (Gateway, Compose, psql-only, or source) that matches the interface your app actually uses.
- local-docker-compose-setup — Reproducible local stack via
docker-compose.yml: pinned images,host.docker.internal,restart: unless-stopped. - local-connection-config — Connect on port 10260 with
--tls,--tlsAllowInvalidCertificates, and SCRAM-SHA-256 for the self-signed local cert. - local-env-driven-config — Drive connection URI and TLS relaxation from env vars; never default
tlsAllowInvalidCertificates=truein code. - local-sample-data-management — Use
SKIP_INIT_DATA+INIT_DATA_PATHwith vetted seed scripts; don't ship the built-insampledbbeyond local demos. - local-ports-and-bindings — Bind published ports to
127.0.0.1and expose only what you use (10260 for Mongo, 9712 for psql). - local-prod-parity — Same connection abstraction and versioned index/seed scripts across local and Azure DocumentDB; integration-test against the real container.
What ships with it
7 files 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.
- 2d ago First seen · 23 lines · 111 tokens per session scan A 677b6a263c47
documentdb-local-deployment is a skill published in the GitHub repository Azure/documentdb-agent-kit (5 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 523 once invoked, about $0.0006 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 skills, from other repositories
docker-management
Manage Docker containers, images, volumes, and Compose.
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
cognee-docker
Use when the user wants to run cognee with Docker or docker compose — trying it out from the prebuilt image, starting the API server in a container, or bringing up the full stack (UI, MCP, Postgres, Neo4j) with compose profiles.
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox…
manage-mounts
Configure which host directories agent containers can access. View, add, or remove mount allowlist entries. Triggers on "mounts", "mount allowlist", "agent access to directories", "container mounts".
test-locally
Build and deploy a full local OpenMetadata stack with Docker to test your connector in the UI. Handles code generation, build optimization, health checks, and guided testing.