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 instructions/azure/documentdb-agent-kit/agents-mdgit 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.02740 | $0.02740 |
| Opus 5 | $0.01370 | $0.01370 |
| Sonnet 5 | $0.00548 | $0.00548 |
| Haiku 4.5 | $0.00274 | $0.00274 |
Grade B, and why
documentdb-agent-kit AGENTS.md scanned grade B with 1 finding 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 yesterday.
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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
**Default to Route B.** Only take Route A when the user **explicitly** says *"use toolbox"* (or unambiguously asks to run the diagnostic scripts / inspect a live local database). Do not run any script on Route B. How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository is an Agent Skills pack for Azure DocumentDB (with MongoDB compatibility) — the managed Azure service built on the open-source DocumentDB project. Every skill targets Azure DocumentDB specifically; rules call out DocumentDB features that differ from community MongoDB (cosmosSearch vector indexes, createSearchIndexes full-text search, cluster M-tiers, Entra RBAC, CMK, etc.).
Status: Public Preview. This kit and its upstream MCP server are pre-GA; rule contents, skill shapes, installer behavior, and the MCP tool surface may change in breaking ways. No SLA. See the Azure Preview Supplemental Terms. When acting on the kit, agents should call out this status to the user if they're about to commit kit-installed configs into anything that looks production-shaped.
How agents should use this kit
This kit has two routes. Decide the route first, from what the user said:
| The user says… | Route | What the agent does |
|---|---|---|
| "use toolbox" (explicit), or clearly asks to run the diagnostic scripts against a live database | Route A — Diagnostic toolbox | Use the knowledge-base router to pick and run a read-only diagnostic script against the user's local DocumentDB container, then report the findings. |
| anything else (the default) | Route B — Text skills | Route to the best skills/*/SKILL.md and answer from guidance. |
Default to Route B. Only take Route A when the user explicitly says "use toolbox" (or unambiguously asks to run the diagnostic scripts / inspect a live local database). Do not run any script on Route B.
Route A — Diagnostic toolbox (only when the user says "use toolbox")
Deterministic, read-only scripts that inspect a local DocumentDB container (both the MongoDB API and the PostgreSQL engine underneath) and emit findings. They never modify data; no cloud, no API keys. Steps:
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.
- yesterday First seen · 127 lines · 2,740 tokens per session scan B 9b1fce4cd017
documentdb-agent-kit AGENTS.md is an instructions file published in the GitHub repository Azure/documentdb-agent-kit (5 stars, last pushed 1mo ago), licensed MIT. It adds 2,740 tokens to every session, about $0.0137 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). 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.
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).
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.
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
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.
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.