elastic/cursor-plugins is a collection of Cursor plugins that give AI assistants access to Elastic documentation and guidance for Elastic Cloud, Elasticsearch, Kibana, Observability, and Security. Developers use it when working with Elastic products and related technologies. The catalogue lists these plugins' skills and documentation MCP tools.
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 skills add elastic/cursor-plugins --skill elasticsearch-cluster-healthgit clone --depth 1 https://github.com/elastic/cursor-pluginsWrote 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/skills/elastic/cursor-plugins/elasticsearch-cluster-health)<a href="https://agentmods.dev/skills/elastic/cursor-plugins/elasticsearch-cluster-health"><img src="https://agentmods.dev/badge/skills/elastic/cursor-plugins/elasticsearch-cluster-health/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/skills/elastic/cursor-plugins/elasticsearch-cluster-health"><img src="https://agentmods.dev/badge/skills/elastic/cursor-plugins/elasticsearch-cluster-health.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.00068 | $0.02784 |
| Opus 5 | $0.00034 | $0.01392 |
| Sonnet 5 | $0.00014 | $0.00557 |
| Haiku 4.5 | $0.00007 | $0.00278 |
Grade A, and why
elasticsearch-cluster-health 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 7d 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 elasticsearch-cluster-health — 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose Cluster Health
Triage a non-green Elasticsearch cluster read-only: localize the problem, classify the allocation decider, and report the single most likely cause with remediation. Never mutate cluster state — surface findings and let the operator act.
Environment Configuration
This skill executes Elasticsearch operations through the elastic CLI. If the
elastic CLI is not installed, tell the user what it is needed for. Do
not guess credentials, call the HTTP API directly, or attempt other workarounds.
This skill references operations in HTTP-shorthand form (e.g., GET /, GET /_cat/indices, GET /{index}/_mapping,
GET /{index}/_settings/index.mode, POST /_query). The Operations table at the end of this document
maps each shorthand to the equivalent elastic CLI command — always use the CLI rather than calling the HTTP API
directly.
Process
-
Read the overall status. Call
GET /_cluster/health. Thestatusfield is the verdict:green— every primary and replica is assigned. Report healthy and stop.yellow— every primary is assigned but at least one replica is not. Data remains readable; redundancy is degraded. This is not data loss.red— at least one primary is unassigned. Data for that shard is unavailable; treat as urgent.
Also read
unassigned_shards,initializing_shards, andrelocating_shards. The decision: continue only when status is yellow or red. Ifinitializing_shards > 0andunassigned_shards == 0, the cluster is recovering on its own — callGET /_cat/recoveryto confirm progress, wait, and re-checkGET /_cluster/healthbefore escalating.Data needed: cluster-wide
statusand shard counters. -
Localize the problem to one index. Call
GET /_cluster/health?level=indicesand pick the index that drives the cluster-wide status:- Any red index outranks every yellow index.
- Among reds or yellows, prefer the index with the most
unassigned_shards. - A red system index (
.security,.kibana*,.fleet-*) outranks application indices because the rest of the stack depends on it.
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.
- 7d ago First seen · 174 lines · 68 tokens per session scan A c2e16fcc6ca6
elasticsearch-cluster-health is a skill published in the GitHub repository elastic/cursor-plugins (32 stars, last pushed 8d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,784 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to elasticsearch-cluster-health, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.