kibana-streams

A skill for managing Kibana Streams, an Elastic feature for organizing and controlling data flows in Kibana. It works through Kibana's web API.

In plain words
What is it for?
Use it to list streams, inspect ingest or query settings, view linked dashboards and rules, or enable, disable, and resync streams. It requires a Kibana address and suitable authentication and privileges.
Why use it?
It gives an agent a documented way to inspect stream configuration and control stream lifecycle without guessing API paths or permissions. Stream creation and other broader changes are not covered.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/elastic/cursor-plugins/streams
Any agent
npx skills add elastic/cursor-plugins --skill streams
Clone the repo
git clone --depth 1 https://github.com/elastic/cursor-plugins

Made for: Claude Code, Codex.

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00053 $0.01814
Opus 5 $0.00026 $0.00907
Sonnet 5 $0.00011 $0.00363
Haiku 4.5 $0.00005 $0.00181

Measured 2d ago against content hash 9acd50aac7cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

kibana-streams 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 -X GET "${KIBANA_URL}/api/streams" \
Origin

This is a copy

100% identical to kibana-streams — 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.

elastic/skills/kibana/streams/SKILL.md · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kibana Streams

Read stream metadata, settings, and attachments, and manage stream lifecycle (enable, disable, resync) via the Kibana Streams REST API. Streams are an experimental way to manage data in Kibana — expect API and behavior changes. This skill covers read operations and lifecycle only; create, update, delete, fork, and other mutating operations may be added in a later version.

For detailed endpoints and parameters, see references/streams-api-reference.md.

When to use

  • Listing all streams or getting a single stream's definition and metadata
  • Reading a stream's ingest settings, or the ES|QL definition of a query stream
  • Listing attachments (dashboards, rules, SLOs) linked to a stream
  • Enabling, disabling, or resyncing streams

Prerequisites

Item Description
Kibana URL Kibana endpoint (e.g. https://localhost:5601 or a Cloud deployment URL)
Authentication API key or basic auth (see the elasticsearch-authn skill)
Privileges read_stream for read operations; manage_stream for lifecycle APIs

Use the space-scoped path /s/{space_id}/api/streams when operating in a non-default space. For role configuration (Kibana feature privileges and Elasticsearch-level permissions), refer to Streams required permissions.

API base and headers

  • Base path: GET or POST to <kibana_url>/api/streams (or /s/<space_id>/api/streams for a space).
  • Read operations: Typically do not require extra headers; follow the official API docs for each endpoint.
  • Lifecycle operations: POST /api/streams/_disable, _enable, and _resync are mutating — send kbn-xsrf: true (or equivalent) as required by your Kibana version.

Read the full file on GitHub · 162 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 2d ago First seen · 162 lines · 53 tokens per session scan A 9acd50aac7cd

Subscribe to this mod's changes

kibana-streams is a skill published in the GitHub repository elastic/cursor-plugins (31 stars, last pushed 5d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,814 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to kibana-streams, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens