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/agent-skills/setupnpx skills add elastic/agent-skills --skill setupgit clone --depth 1 https://github.com/elastic/agent-skillsWhat 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}" \ Copies of this mod
1 near-identical copy found in the catalogue:
- cloud-setup — 100% identical, 0 lines differ
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/agent-skills (564 stars, last pushed 6d 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
huggingface-spaces
Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't…
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.