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 G1Joshi/Agent-Skills --skill cosmosdbgit clone --depth 1 https://github.com/G1Joshi/Agent-SkillsWrote 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/g1joshi/agent-skills/cosmosdb)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/cosmosdb"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/cosmosdb/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/g1joshi/agent-skills/cosmosdb"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/cosmosdb.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.00454 |
| Opus 5 | $0.00009 | $0.00227 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
cosmosdb 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 5d 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
Azure Cosmos DB
Cosmos DB is Azure's planetary-scale database. It supports multiple APIs: NoSQL (Core/JSON), MongoDB, PostgreSQL, Cassandra, Gremlin (Graph), and Table.
When to Use
- Global Distribution: Replicate data to any Azure region with a click.
- Multi-Model: If you need Mongo or Postgres APIs but want "PaaS" management.
- Low Latency: Guaranteed <10ms read/write latency at the 99th percentile.
Quick Start (NoSQL API)
Container container = database.GetContainer("Items");
Item item = new Item
{
Id = "1",
Category = "Personal",
Name = "Groceries"
};
await container.CreateItemAsync(item, new PartitionKey(item.Category));
Core Concepts
Request Units (RUs)
The currency of Cosmos DB. Use RUs to pay for throughput. 1 RU ≈ reading a 1KB doc.
Partition Key
Crucial. Determines how data is distributed. A bad partition key ("Date") creates "Hot Partitions" (bottlenecks). A good key ("UserId") distributes load evenly.
Consistency Levels
Offers 5 levels: Strong, Bounded Staleness, Session (Default), Consistent Prefix, Eventual. Trade off consistency for availability/latency.
Best Practices (2025)
Do:
- Use the NoSQL API: It is the native API with the most features.
- Use Hierarchical Partition Keys (2025): Supports up to 3 keys for better data distribution (TenantId -> UserId -> DeviceId).
- Use Analytical Store (Synapse Link): Run heavy analytics (BI) on your operational data without impacting performance.
Don't:
- Don't ignore RU consumption: Monitor it. Queries without a partition key ("Cross-partition queries") are expensive.
References
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.
- 5d ago First seen · 60 lines · 18 tokens per session scan A 21fc601bc0d3
cosmosdb is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 454 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
backup-restore
PostgreSQL backup and restore with pgBackRest — full/incremental/WAL, PITR, K8s CronJob scheduling, and restore verification.
db-performance
PostgreSQL query performance — EXPLAIN ANALYZE, index design, pgstatstatements, slow query detection, connection pool tuning.
postgres-operations
PostgreSQL operational runbooks — health checks, vacuum, bloat, locks, PITR, connection pool management.
alloydb-omni-kubernetes
You're an expert in AlloyDB Omni Operator running in Kubernetes. You can help users with related tasks such as creating, managing, and monitoring AlloyDB Omni DBClusters.
alloydb-omni-container
You're an expert in AlloyDB Omni running in a container. You can help users with related tasks such as starting, stopping, listing, connecting to AlloyDB Omni instance running in a container, and querying for logs.
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB model context protocol (MCP) tools for automated database operations.