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 agentmods add rules/prisma/prisma-next/mongo-no-obsolete-commandsgit clone --depth 1 https://github.com/prisma/prisma-nextWrote 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/rules/prisma/prisma-next/mongo-no-obsolete-commands)<a href="https://agentmods.dev/rules/prisma/prisma-next/mongo-no-obsolete-commands"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/mongo-no-obsolete-commands.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00239 |
| Opus 5 | $0.00010 | $0.00120 |
| Sonnet 5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
mongo-no-obsolete-commands 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.
This is a copy
100% identical to mongo-no-obsolete-commands — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
MongoDB: no obsolete commands
MongoDB's find and findOne are legacy commands from older MongoDB versions. The MongoDB product team considers them obsolete.
Use aggregate instead of find/findOne
// BAD — obsolete command
const doc = await db.collection('foo').findOne({ _id: id });
// GOOD — modern aggregate pipeline
const docs = await db
.collection('foo')
.aggregate([{ $match: { _id: id } }, { $limit: 1 }])
.toArray();
const doc = docs[0] ?? null;
For multiple documents, use aggregate with $match (and $sort, $skip, $limit as needed) instead of find().sort().skip().limit().
insertOne, findOneAndUpdate, findOneAndDelete are fine
These are standard CRUD operations and are not obsolete. Continue using them directly.
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 · 29 lines · 20 tokens per session scan A 13d89da1ee71
mongo-no-obsolete-commands is a cursor rule published in the GitHub repository prisma/prisma-next (419 stars, last pushed 10d ago), licensed Apache-2.0. It adds 20 tokens to every session and 239 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mongo-no-obsolete-commands, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
mongo-no-obsolete-commands
Use MongoDB aggregate instead of the obsolete find/findOne commands.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .