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.
git clone --depth 1 https://github.com/AzureCosmosDB/cosmosdb-claude-code-pluginWrote 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/commands/azurecosmosdb/cosmosdb-claude-code-plugin/cosmos-review)<a href="https://agentmods.dev/commands/azurecosmosdb/cosmosdb-claude-code-plugin/cosmos-review"><img src="https://agentmods.dev/badge/commands/azurecosmosdb/cosmosdb-claude-code-plugin/cosmos-review/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/commands/azurecosmosdb/cosmosdb-claude-code-plugin/cosmos-review"><img src="https://agentmods.dev/badge/commands/azurecosmosdb/cosmosdb-claude-code-plugin/cosmos-review.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.00012 | $0.00308 |
| Opus 5 | $0.00006 | $0.00154 |
| Sonnet 5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
cosmos-review 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 9d 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
Cosmos DB Code Review
Review the user's code against Azure Cosmos DB best practices. Use the cosmosdb-best-practices skill as your reference.
Review Checklist (in priority order)
CRITICAL
- Data model design (embedding vs referencing, document size)
- Partition key choice (cardinality, query alignment, hot partitions)
- CosmosClient lifecycle (singleton pattern)
HIGH
- Query optimization (cross-partition, projections, pagination)
- SDK patterns (async, connection mode, retry configuration)
- Concurrency control (ETags for read-modify-write)
- Design patterns (Change Feed, materialized views)
MEDIUM
- Indexing strategy (exclude unused paths, composite indexes)
- Throughput configuration (autoscale vs fixed, right-sizing)
- Global distribution (preferred regions, consistency level)
LOW-MEDIUM
- Monitoring (diagnostics logging, RU tracking, alerts)
Output Format
For each finding:
- Rule: Which best practice rule applies
- Severity: CRITICAL / HIGH / MEDIUM / LOW
- Current code: What the code does now
- Issue: Why it's problematic (with RU/latency/scalability impact)
- Fix: Corrected code example
$ARGUMENTS
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.
- 9d ago First seen · 40 lines · 12 tokens per session scan A 217dad02376e
cosmos-review is a command published in the GitHub repository AzureCosmosDB/cosmosdb-claude-code-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 308 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-08-30.
Other commands, from other repositories
pg-indexes
Review unused indexes that are safe to drop (pgbot).
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
inventory
Codebase inventory skill — scans the repo for a named pattern (inline SQL, fetch calls, feature flags, debug leftovers, deprecated APIs, etc.) and emits a structured Markdown inventory cross-referenced with framework metadata (routes, handlers). Language-agnostic and pack-driven — the engine matches whatever a YAML…
review
Run the altimate-code dbt/SQL PR reviewer on the current diff, PR, or commit and present the signed verdict verbatim.
schema-gate
Review a pending DB migration. Static checks (drops/renames/truncates) run as a deterministic shell pre-pass; live-DB checks (RLS, index size, forward-compat) run via a Haiku subagent. Read-only.
db-object-audit-review
Internal RA review of db object audit.