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 skills add AzureCosmosDB/cosmosdb-agent-kit --skill cosmosdb-best-practicesgit clone --depth 1 https://github.com/AzureCosmosDB/cosmosdb-agent-kitWrote 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/azurecosmosdb/cosmosdb-agent-kit/cosmosdb-best-practices)<a href="https://agentmods.dev/skills/azurecosmosdb/cosmosdb-agent-kit/cosmosdb-best-practices"><img src="https://agentmods.dev/badge/skills/azurecosmosdb/cosmosdb-agent-kit/cosmosdb-best-practices/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/azurecosmosdb/cosmosdb-agent-kit/cosmosdb-best-practices"><img src="https://agentmods.dev/badge/skills/azurecosmosdb/cosmosdb-agent-kit/cosmosdb-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk pass
- NVIDIA SkillSpector pass
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.1 | $0.00177 | $0.04856 |
| Opus 5.5 | $0.00071 | $0.01942 |
| Sonnet 5.5 | $0.00035 | $0.00971 |
| Haiku 4.5 | $0.00018 | $0.00486 |
Grade A, and why
cosmosdb-best-practices 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 3d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Cosmos DB Best Practices
Comprehensive performance optimization guide for Azure Cosmos DB applications, containing 100+ rules across 13 categories, prioritized by impact to guide automated refactoring and code generation.
Before answering, read the linked rule files relevant to the user's question. The quick reference below is an index, not the full guidance: SDK APIs, limits, configuration prerequisites, and caveats live in the rule bodies. Use the language-specific integration rule when one exists rather than substituting a generic pattern. Keep answers concise, but include the constraints that make the recommendation correct for the user's scenario.
When to Apply
Reference these guidelines when:
- Designing data models for Cosmos DB
- Choosing partition keys
- Writing or optimizing queries
- Implementing SDK patterns
- Using the Cosmos DB Emulator for local development
- Inspecting or managing Cosmos DB data with developer tooling
- Implementing vector search or RAG features on Cosmos DB
- Reviewing code for performance issues
- Configuring throughput and scaling
- Building globally distributed applications
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Data Modeling | CRITICAL | model- |
| 2 | Partition Key Design | CRITICAL | partition- |
| 3 | Query Optimization | HIGH | query- |
| 4 | SDK Best Practices | HIGH | sdk- |
| 5 | Indexing Strategies | MEDIUM-HIGH | index- |
| 6 | Throughput & Scaling | MEDIUM | throughput- |
| 7 | Global Distribution | MEDIUM | global- |
| 8 | Monitoring & Diagnostics | LOW-MEDIUM | monitoring- |
| 9 | Design Patterns | HIGH | pattern- |
| 10 | Developer Tooling | MEDIUM | tooling- |
| 11 | Vector Search | HIGH | vector- |
| 12 | Full-Text Search | HIGH | fts- |
| 13 | Security | HIGH | security- |
Quick Reference
1. Data Modeling (CRITICAL)
- model-embed-related - Embed related data retrieved together
- model-reference-large - Reference data when items get too large
- model-avoid-2mb-limit - Keep items well under 2MB limit
- model-id-constraints - Follow ID value length and character constraints
- model-unique-keys - Enforce business-key uniqueness within the correct logical partition scope
- model-nesting-depth - Stay within 128-level nesting depth limit
- model-numeric-precision - Understand IEEE 754 numeric precision limits
- model-denormalize-reads - Denormalize for read-heavy workloads including pre-computed aggregates
- model-schema-versioning - Version your document schemas
- model-type-discriminator - Use type discriminators for polymorphic data
- model-json-serialization - Handle JSON serialization correctly for Cosmos DB documents
- model-relationship-references - Use ID references with transient hydration for document relationships
- model-ttl-expiration - Configure TTL relative to the item's last update, with container defaults and item overrides
What ships with it
60 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.
- agents/openai.yaml 310 B
- metadata.json 590 B
- README.md 4.8 KB
- rules/_sections.md 3.0 KB
- rules/_template.md 1.0 KB
- rules/fts-add-index.md 1.9 KB
- rules/fts-define-policy.md 1.7 KB
- rules/fts-enable-capability.md 1.6 KB
- rules/fts-hybrid-queries.md 2.3 KB
- rules/fts-keyword-matching.md 2.2 KB
- rules/fts-relevance-ranking.md 1.4 KB
- rules/global-conflict-resolution.md 4.0 KB
- rules/global-consistency.md 3.9 KB
- rules/global-failover.md 3.7 KB
- rules/global-multi-region-write-antipattern.md 2.6 KB
- rules/global-multi-region.md 3.2 KB
- rules/global-read-regions.md 3.9 KB
- rules/global-zone-redundancy.md 3.5 KB
- rules/index-composite-direction.md 2.8 KB
- rules/index-composite.md 12 KB
- rules/index-exclude-unused.md 4.0 KB
- rules/index-lazy-consistent.md 3.3 KB
- rules/index-path-syntax.md 2.5 KB
- rules/index-range-vs-hash.md 3.9 KB
- rules/index-spatial.md 3.1 KB
- rules/model-avoid-2mb-limit.md 2.0 KB
- rules/model-denormalize-reads.md 12 KB
- rules/model-embed-related.md 2.5 KB
- rules/model-id-constraints.md 7.4 KB
- rules/model-json-serialization.md 6.0 KB
- rules/model-nesting-depth.md 3.3 KB
- rules/model-numeric-precision.md 3.2 KB
- rules/model-reference-large.md 2.3 KB
- rules/model-relationship-references.md 3.6 KB
- rules/model-schema-versioning.md 2.8 KB
- rules/model-ttl-expiration.md 3.1 KB
- rules/model-type-discriminator.md 3.5 KB
- rules/model-unique-keys.md 5.3 KB
- rules/monitoring-azure-monitor.md 4.4 KB
- rules/monitoring-diagnostic-logs.md 5.1 KB
- rules/monitoring-latency.md 4.2 KB
- rules/monitoring-ru-consumption.md 7.5 KB
- rules/monitoring-throttling.md 4.4 KB
- rules/partition-20gb-limit.md 2.8 KB
- rules/partition-avoid-hotspots.md 3.4 KB
- rules/partition-hierarchical.md 5.7 KB
- rules/partition-high-cardinality.md 2.2 KB
- rules/partition-immutable-key.md 1.8 KB
- rules/partition-key-length.md 2.8 KB
- rules/partition-query-patterns.md 2.7 KB
- rules/partition-rekey-migration.md 4.4 KB
- rules/partition-synthetic-keys.md 3.8 KB
- rules/pattern-ai-grounding-access.md 4.7 KB
- rules/pattern-background-task-writes.md 2.8 KB
- rules/pattern-change-feed-materialized-views.md 11 KB
- rules/pattern-efficient-ranking.md 5.9 KB
- rules/pattern-langgraph-agent-name-attribution.md 2.2 KB
- rules/pattern-langgraph-agent-routing-cosmosdb.md 4.6 KB
- rules/pattern-langgraph-async-cosmos-routing.md 3.2 KB
- rules/pattern-langgraph-async-cosmos-writes.md 2.9 KB
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.
- 3d ago Changed · +35 lines 00e0c45a266c
- 1mo ago Changed 296e63816a70
- 2mo ago First seen · 220 lines · 177 tokens per session scan A c46a4a6ab5d2
cosmosdb-best-practices is a skill published in the GitHub repository AzureCosmosDB/cosmosdb-agent-kit (61 stars, last pushed yesterday), licensed MIT. It adds 177 tokens to every session and 4,856 once invoked, about $0.0007 per session on Opus 5.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
system-design-data-architecture
Design system data flows and data-layer ownership, consistency, and store choices from access patterns. Use for critical-flow design, DFD semantic review, data lineage, authority, replication, retention, or a data-tier bottleneck. Avoid unrelated framework stream/dataframe implementation questions.
pocketbase-best-practices
PocketBase development best practices covering collection design, API rules, authentication, SDK usage, query optimization, realtime subscriptions, file handling, deployment, and server-side extending (Go + JSVM). Current as of PocketBase v0.40 and JS SDK v0.28. Use when building PocketBase backends, designing…
api-design
A guide to designing application interfaces that other software can use, including REST, GraphQL, and gRPC APIs.
database
A guide to database structure, data migrations, queries, and indexes. A database stores application data; a migration changes its structure, and an index helps it find data faster.
domain-modeling
Use when introducing, reviewing, or renaming a top-level type, table, or domain concept; or choosing where state lives (in-memory vs persistent).
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.