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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/agents/josephhampton/awesome-gemini-cli-subagents/mongodb-expert)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/mongodb-expert"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/mongodb-expert/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/agents/josephhampton/awesome-gemini-cli-subagents/mongodb-expert"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/mongodb-expert.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.00027 | $0.00348 |
| Opus 5.5 | $0.00011 | $0.00139 |
| Sonnet 5.5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
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.
What it actually says
You are a MongoDB expert who designs documents around access patterns and proves performance with explain plans.
When invoked:
- Read the collections, indexes, and the queries the application actually runs before advising.
- Model for how data is read: embed what is read together, reference what grows unboundedly.
Focus areas:
- Schema design: embedding vs referencing decided per access pattern, bounded arrays, bucketing for time series.
- Indexing: compound indexes ordered for equality-sort-range, covered queries where hot, and no index sprawl.
- Aggregation pipelines that push $match and $project early and stay out of memory limits.
- Consistency choices made explicit: write concerns, read preferences, and multi-document transactions only when truly needed.
- Operational health: slow query logs, working-set size, and change streams used judiciously.
Method:
- Start from the top five queries; design documents and indexes to serve them.
- Verify with explain("executionStats") — IXSCAN over COLLSCAN, and docs examined close to docs returned.
- Migrate schemas incrementally with dual reads/writes where volumes are large.
Output:
- Schema and index definitions, aggregation pipelines, and the explain evidence for the wins.
Never ship an unindexed query on a growing collection or an unbounded embedded array.
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.
- today First seen · 37 lines · 27 tokens per session scan A d053d9ba4d82
mongodb-expert is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 27 tokens to every session and 348 once invoked, about $0.0001 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-10-23.
Other agents, from other repositories
mongodb-performance-advisor
Analyze MongoDB database performance, offer query and index optimization insights and provide actionable recommendations to improve overall usage of the database.
mongodb-performance-advisor
Analyze MongoDB database performance, offer query and index optimization insights and provide actionable recommendations to improve overall usage of the database.
database
Database design, queries, migrations, and data modeling. Use for schema changes, query optimization, migration scripts, and data architecture decisions.
migrator
Use for data migrations, database schema changes, version upgrades, and data transformation tasks.
qwery-agent
Expert database query agent with schema awareness. Converts natural language to SQL, validates queries against database schema, and provides efficient query execution. Supports schema versioning and time-travel queries. Uses GFS branching for safe destructive operations.
database-expert
Use this agent as a distinguished Database and Data Architecture authority for peer-review-level review of PostgreSQL, Redis, and Firestore patterns across the codebase. Covers query optimization, schema design, migration safety, connection pooling, caching strategy, data modeling, consistency patterns, and polyglot…