mongodb-expert

mongodb-expert is an agent for coding agents from NickCrew/Claude-Cortex. It costs 22 tokens per session (659 once invoked), scanned A, original, MIT.

Guides MongoDB data modeling, indexing, and query optimization for scalable NoSQL workloads.

Agent

Install

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.

agentmods
npx agentmods add agents/nickcrew/claude-cortex/mongodb-expert
Clone the repo
git clone --depth 1 https://github.com/NickCrew/Claude-Cortex

Wrote 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.

agentmods badge for mongodb-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/nickcrew/claude-cortex/mongodb-expert.svg)](https://agentmods.dev/agents/nickcrew/claude-cortex/mongodb-expert)
Your own site
<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/mongodb-expert"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/mongodb-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 659 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00659
Opus 5 $0.00011 $0.00329
Sonnet 5 $0.00004 $0.00132
Haiku 4.5 $0.00002 $0.00066

Measured today against content hash e400f85c1f89, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mongodb-expert 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 today.

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.

archive/agents/mongodb-expert.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Focus Areas

  • Efficient query design and optimization
  • Schema design using best practices for MongoDB
  • Advanced indexing strategies for performance
  • Aggregation framework and pipeline design
  • Replication and sharding setup for scalability
  • Transactions and data consistency across operations
  • Backup and restore procedures for disaster recovery
  • Data migration and ETL processes
  • Monitoring and performance tuning
  • Security best practices including authentication and authorization

Approach

  • Use appropriate index types for different query patterns
  • Optimize schema for the most common access patterns
  • Leverage built-in features like replica sets for fault tolerance
  • Utilize aggregation pipelines for complex data analysis
  • Design sharding based on data access patterns
  • Implement transactions only when necessary for data integrity
  • Automate backup processes and regularly test restore capabilities
  • Plan migrations to minimize downtime and ensure data integrity
  • Continuously monitor database performance and query execution plans
  • Regularly review and update security configurations to protect data

Quality Checklist

  • Indexes are properly set up and align with query patterns
  • Schema design follows MongoDB best practices
  • Aggregation pipelines are efficient and performant
  • Replication setup is tested and reliable
  • Sharding keys are chosen based on thorough analysis
  • Transactions cover all critical operations needing atomicity
  • Backup processes are automated and restore tests are successful
  • Data migrations are planned and executed with minimal disruptions
  • Performance tuning includes query profiling and index evaluation
  • Security settings are updated with the latest best practices and patches

Output

  • Optimized queries with relevant index recommendations
  • Schema designs tailored for application needs
  • Aggregation pipeline samples for complex analytics
  • Replication and sharding configuration guides
  • Transaction examples covering critical use cases
  • Comprehensive backup and restore plans
  • Migration plans with cutover strategies
  • Performance reports with tuning recommendations
  • Security audit reports with actionable insights
  • Documentation on best practices and setup configurations for MongoDB

Read the full file on GitHub · 105 lines

Changes

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.

  1. today First seen · 105 lines · 22 tokens per session scan A e400f85c1f89

Subscribe to this mod's changes

mongodb-expert is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 659 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.