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 skills/elastic/cursor-plugins/setupnpx skills add elastic/cursor-plugins --skill setupgit clone --depth 1 https://github.com/elastic/cursor-pluginsWhat 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.00034 | $0.01046 |
| Opus 5 | $0.00017 | $0.00523 |
| Sonnet 5 | $0.00007 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
cloud-setup scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: ApiKey ${EC_API_KEY}" \ This is a copy
100% identical to cloud-setup — 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Environment Setup
Configure Elastic Cloud authentication and preferences. All other cloud/* skills depend on this setup.
Workflow
Setup Progress:
- [ ] Step 1: Verify API key
- [ ] Step 2: Set defaults
- [ ] Step 3: Validate connection
Step 1: Verify API key
Check whether EC_API_KEY is already set:
echo "${EC_API_KEY:?Not set}"
If not set, instruct the user to set it. Never ask the user to paste an API key into the chat — secrets must not appear in conversation history.
If the user indicates they do not have an Elastic Cloud account yet, propose starting a free trial at Elastic Cloud free trial. The trial provides 14 days of full access to Elastic Cloud Serverless with no credit card required. Once the user has registered and logged in, proceed with API key generation below.
Direct the user to:
- Generate a key at Elastic Cloud API keys. Only Organization owners can create and manage Cloud API keys.
- When creating this key, include Project Admin privileges or higher (Org Owner) so it can create and manage serverless projects.
- Create a
.envfile in the project root (recommended — works in sandboxed agent shells):
EC_API_KEY=your-api-key
All cloud/* scripts auto-load .env from the working directory — no manual sourcing needed.
Alternatively, export directly in the terminal:
export EC_API_KEY="your-api-key"
Terminal exports might not be visible to sandboxed agents running in a separate shell session. Prefer the .env file
when working with an agent.
Remind the user that storing secrets in local files is acceptable for development, but for production or shared environments, use a centralized secrets manager (for example, HashiCorp Vault, AWS Secrets Manager, 1Password CLI) to avoid secrets sprawl.
Step 2: Set defaults
Export the base URL and default region:
export EC_BASE_URL="https://api.elastic-cloud.com"
export EC_REGION="gcp-us-central1"
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.
- 2d ago First seen · 139 lines · 34 tokens per session scan A bb63882b97b8
cloud-setup is a skill published in the GitHub repository elastic/cursor-plugins (31 stars, last pushed 5d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,046 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to cloud-setup, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…