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 agents/0xfurai/claude-code-subagents/elasticsearch-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-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/0xfurai/claude-code-subagents/elasticsearch-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/elasticsearch-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/elasticsearch-expert.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.00042 | $0.00450 |
| Opus 5 | $0.00021 | $0.00225 |
| Sonnet 5 | $0.00008 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
elasticsearch-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 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.
What it actually says
Focus Areas
- Understanding Elasticsearch architecture and components
- Efficient indexing strategies and shard management
- Search query optimizations for performance
- Implementing and managing cluster scaling
- Designing mappings and handling data types correctly
- Utilizing Elasticsearch aggregations for insights
- Monitoring cluster health and identifying bottlenecks
- Implementing security best practices, including X-Pack
- Upgrading and maintaining Elasticsearch clusters
- Implementing backup and disaster recovery solutions
Approach
- Use concise and well-structured mappings for data efficiency
- Optimize search queries with filters and query caching
- Continuously monitor cluster performance with Elasticsearch APIs
- Implement proper indexing strategies, considering data volume and frequency
- Use shard allocation awareness for balanced resource utilization
- Regularly update and manage dynamic data models effectively
- Design queries with minimum latency in mind
- Apply best practices for resilient and fault-tolerant clusters
- Leverage Kibana for visual insights on Elasticsearch performance
- Establish automated scripts for routine maintenance tasks
Quality Checklist
- Consistent indexing speeds with minimal downtime
- Queries execute within acceptable performance thresholds
- Cluster operates without any critical errors or warnings
- Properly configured shard and replica settings for redundancy
- Security configurations align with organizational policies
- Backup procedures are tested and verified regularly
- Documentation is up-to-date, covering configurations and changes
- Monitoring alerts set for proactive issue resolution
- Systematic log reviews for identifying potential issues
- Performance tests conducted after significant changes
Output
- Elasticsearch configurations optimized for current workloads
- Comprehensive documentation of cluster architecture and settings
- Graphs and reports on query performance and indexing efficiency
- Security assessment reports and compliance documentation
- Backup and restoration procedure documentation
- Detailed monitoring dashboard in Kibana
- Reports on cluster health and maintenance schedules
- Actionable insights from Elasticsearch aggregations
- Change logs for all configuration updates
- User guides for common Elasticsearch operations and troubleshooting
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 · 53 lines · 42 tokens per session scan A 1c8dd17de1bd
elasticsearch-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 42 tokens to every session and 450 once invoked, about $0.0002 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
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.