MongoDB Java Driver is a set of libraries that lets Java, Kotlin, and Scala applications connect to and work with MongoDB databases. JVM developers use the drivers to build database-backed applications in those languages. The catalogue instructions and skills support development involving these drivers.
Borrowing it
Nothing to install: this file belongs to mongodb/mongo-java-driver. 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/mongodb/mongo-java-driver/main/AGENTS.mdgit clone --depth 1 https://github.com/mongodb/mongo-java-driverWrote 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/mongodb/mongo-java-driver/agents-md)<a href="https://agentmods.dev/instructions/mongodb/mongo-java-driver/agents-md"><img src="https://agentmods.dev/badge/instructions/mongodb/mongo-java-driver/agents-md/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/mongodb/mongo-java-driver/agents-md"><img src="https://agentmods.dev/badge/instructions/mongodb/mongo-java-driver/agents-md.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.01067 | $0.01067 |
| Opus 5.5 | $0.00427 | $0.00427 |
| Sonnet 5.5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
mongo-java-driver AGENTS.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 1mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - MongoDB Java Driver
All changes require human review.
Breaking changes to public API require a major version bump — always warn if binary compatibility is affected.
Also consult .AGENTS.md / ~/.AGENTS.md if present for local agent settings.
Architecture: Multi-module Gradle project: bson → driver-core → driver-sync/driver-reactive-streams → language wrappers (driver-kotlin-sync, driver-kotlin-coroutine, driver-scala).
See .agents/references/project-guide for module structure and dependency graph.
Each module has its own AGENTS.md.
Git
The default branch is main (not master). Always use main when comparing, diffing, or creating branches.
- Branch naming:
JAVA-XXXXmatching the Jira ticket (e.g.,JAVA-6143) - Commits: Keep commits logical and reviewable — each commit should be a coherent unit of change
- TODO comments: Must reference a Jira ticket if the work belongs to a different ticket:
// TODO JAVA-XXXX reasoning for the todo
Core Rules
- Read before modifying — understand existing code and patterns first
- Minimal changes only — no drive-by refactoring or unrelated changes
- Preserve existing comments — only remove if provably incorrect
- No rewrites without explicit permission
- When stuck or uncertain: stop, explain, propose alternatives, ask
- When authoring or reviewing changes: consult the relevant
.agents/references/file for each area the changes touch
Build
Gradle with Kotlin DSL. Build JDK: 17+. Source baseline: Java 8. Versions in gradle/libs.versions.toml.
- Java 8 baseline: no Java 9+ language features unless the module raises
sourceCompatibility. - Kotlin 1.8 with JVM target 1.8; all Kotlin modules enforce
explicitApi().
Details for both are in .agents/references/style-reference.
./gradlew check # Full validation (format + static checks + tests)
./gradlew :driver-core:test # Single module tests
./gradlew integrationTest -Dorg.mongodb.test.uri="mongodb://localhost:27017"
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.
- 1mo ago Changed · +7 lines · +70 tokens per session 3e5961fa7b8e
- 2mo ago First seen · 99 lines · 997 tokens per session scan A 084be397b8d7
mongo-java-driver AGENTS.md is an instructions file published in the GitHub repository mongodb/mongo-java-driver (2,661 stars, last pushed today), licensed Apache-2.0. It adds 1,067 tokens to every session, about $0.0043 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
vibetags com-example-indexed-core-DocumentIndexEntry.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for documentindexentry, core functionality, rules for method comparebysequence, thread-safety guarantee and architectural boundary constraints.
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).