Borrowing it
Nothing to install: this file belongs to AzureCosmosDB/cosmosdb-agent-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AzureCosmosDB/cosmosdb-agent-kit/main/.github/instructions/code-review.instructions.mdgit 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/instructions/azurecosmosdb/cosmosdb-agent-kit/code-review)<a href="https://agentmods.dev/instructions/azurecosmosdb/cosmosdb-agent-kit/code-review"><img src="https://agentmods.dev/badge/instructions/azurecosmosdb/cosmosdb-agent-kit/code-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/instructions/azurecosmosdb/cosmosdb-agent-kit/code-review"><img src="https://agentmods.dev/badge/instructions/azurecosmosdb/cosmosdb-agent-kit/code-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.00897 | $0.00897 |
| Opus 5.5 | $0.00359 | $0.00359 |
| Sonnet 5.5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
cosmosdb-agent-kit code-review.instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When performing a code review, apply these checks for the cosmosdb-agent-kit repository.
The full checklist, field requirements, and per-section details live in
.github/skills/code-review/checklist.md
— read that file for the complete rules. This file summarizes the key gates.
Severity Tiers
- 🔴 Blocking: Must fix before merge.
- 🟡 Recommendation: Should fix.
- 🟢 Suggestion: Nice to have.
Key Gates (🔴 Blocking)
Rule files (skills/*/rules/*.md):
- Frontmatter:
title,impact(CRITICAL|HIGH|MEDIUM-HIGH|MEDIUM|LOW-MEDIUM|LOW),impactDescription,tags - Body:
**Incorrect+**Correctsections with fenced code blocks - Filename:
{prefix}-{description}.md(model-, partition-, query-, sdk-, index-, throughput-, global-, monitoring-, pattern-, tooling-, vector-)
Build:
AGENTS.mdis generated on demand (npm run build) and is not committed; do not require it in rule PRs
Eval tasks (evals/**/*.yaml):
- Vally specs require
nameand non-emptystimuli; each stimulus needs a uniquename,tags,prompt(orturns), and meaningfulgraders - Skill evaluations must check activation (or non-activation) and response correctness, not only completion
Test scenarios (testing-v2/scenarios/):
api-contract.yaml: camelCase fields,health:section requiredtests/conftest.py: deterministic data only — no uuid4(), random, faker
Scripts: Changes to compile.js/validate.js must not break existing rules.
Workflows: No hardcoded secrets. Use ${{ secrets.* }} or ${{ github.token }}.
General: No secrets, API keys, or connection strings anywhere.
Rule Provenance (🔴 Blocking)
Rules in this repo are created by the automated evaluation loop (LLM reviews test failures and proposes rules). Flag rules that show signs of LLM confabulation rather than verified Cosmos DB knowledge:
- 🔴 Claims specific RU costs, internal limits, or SDK implementation details without a verifiable documentation link
- 🔴 Attributes a test failure to a Cosmos DB "best practice" that may actually be a framework bug, test misconfiguration, or code generation error
- 🔴 Invents SDK method signatures, parameters, or behaviors that don't exist in official SDK docs
- 🔴 Presents a scenario-specific workaround as a universal rule (e.g., "always do X" when X only applies to the exact test that failed)
- 🟡 Rule has no Reference link to official Microsoft documentation — high hallucination risk
- 🟡 Rule's Incorrect/Correct examples look synthetic rather than drawn from real SDK usage patterns
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 Changed · +1 lines · +37 tokens per session d56b1fedbc0d
- 2mo ago First seen · 75 lines · 860 tokens per session scan A cd6bfa3816f8
cosmosdb-agent-kit code-review.instructions.md is an instructions file published in the GitHub repository AzureCosmosDB/cosmosdb-agent-kit (61 stars, last pushed 2d ago), licensed MIT. It adds 897 tokens to every session, about $0.0036 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 instructions, from other repositories
vscode buildNext.instructions.md
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
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, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.