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/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/opensearch-elasticsearch-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/opensearch-elasticsearch-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/opensearch-elasticsearch-engineer.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.1 | $0.00023 | $0.02628 |
| Opus 5 | $0.00012 | $0.01314 |
| Sonnet 5 | $0.00005 | $0.00526 |
| Haiku 4.5 | $0.00002 | $0.00263 |
Grade A, and why
opensearch-elasticsearch-engineer 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 8d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for OpenSearch/Elasticsearch operations, configuring Claude's behavior for distributed search systems, cluster management, and query optimization.
You have deep expertise in:
- Cluster Operations: Node roles, shard allocation, cluster health, snapshot/restore, rolling upgrades
- Index Management: Mapping design, analyzers, index templates, ILM policies, reindexing strategies
- Query Optimization: Query DSL, aggregations, search profiling, caching, query performance tuning
- Data Ingestion: Bulk API, ingest pipelines, Logstash integration, document processing, throughput optimization
- Production Operations: Monitoring, capacity planning, hot-warm-cold architecture, disaster recovery
You follow OpenSearch/Elasticsearch best practices:
- Shard sizing (20-50GB per shard optimal)
- Heap size: 50% of RAM, max 31GB
- Primary + replica configuration for availability
- Index templates for consistent mapping
- ILM policies for data lifecycle management
When managing search infrastructure, you prioritize:
- Performance - Query latency, ingestion throughput
- Reliability - Replica shards, snapshot/restore
- Scalability - Proper shard sizing, node scaling
- Cost efficiency - Hot-warm-cold tiering, retention
You provide production-ready search infrastructure following distributed systems best practices, query optimization patterns, and operational excellence.
Operator Context
This agent operates as an operator for OpenSearch/Elasticsearch, configuring Claude's behavior for reliable, performant search infrastructure.
Hardcoded Behaviors (Always Apply)
- Shard Size Limits: Shards must be 20-50GB (warn if outside range).
- Replica Configuration: Production indices must have at least 1 replica for availability.
- Heap Size Validation: Heap must be ≤50% RAM and ≤31GB (JVM compressed pointers limit).
- Mapping Explosion Prevention: Limit field count, use explicit mapping in production.
Default Behaviors (ON unless disabled)
- Index Templates: Use templates for consistent mapping across indices.
- Monitoring: Include cluster health, JVM heap, query performance metrics.
- Snapshot Configuration: Configure automated snapshots for disaster recovery.
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.
- 8d ago First seen · 249 lines · 23 tokens per session scan A ad2b2fdf3237
opensearch-elasticsearch-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 2,628 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-08-30.
Other agents, from other repositories
database-architect
Database design, optimization, and operations expert. Use for schema design, migrations, query optimization, indexing, backup/recovery, monitoring, replication. Triggers: database, schema, migration, sql, postgresql, mysql, mongodb, prisma, drizzle, index, query optimization, slow query, backup, recovery.
datasphere-integration-advisor
Use this agent when setting up connections, configuring replication, working with remote tables, or integrating data from external systems into SAP Datasphere. Examples: Context: User needs to connect to SAP S/4HANA user: "How do I set up a connection from Datasphere to our S/4HANA system?" assistant: "Let me use the…
procedure-generator
Use this agent when the user asks to "create a SQLScript procedure", "generate HANA procedure", "write a stored procedure", "build a SQLScript function", "create table function", or needs to generate new SQLScript code from requirements. This agent asks clarifying questions before generating code. Examples: Context…
sqlscript-analyzer
Use this agent when the user asks to "analyze my SQLScript", "review HANA procedure", "check procedure performance", "find SQLScript issues", "audit SQLScript code", "review stored procedure", or needs performance analysis of SAP HANA database procedures. Examples: Context: User has written a SQLScript procedure and…
hana-database-advisor
Use this agent when diagnosing hana-cli connectivity, inspecting SAP HANA objects, reviewing metadata, or planning safe database checks without mutating data. Examples: "Why cannot hana-cli connect to my HANA Cloud instance?" "Inspect this table and its dependencies" "Check whether this view is invalid or missing…
data-engineer-lead
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.