embeddable

A generator for Kibana Embeddables, which are custom panels that can be placed inside dashboards or other Kibana containers.

In plain words
What is it for?
Use it to build dashboard widgets that show custom content or visualizations, accept configuration or data, query Elasticsearch or Saved Objects, and emit events such as filter clicks or drilldowns.
Why use it?
It removes the repetitive setup for registering a panel, defining its inputs and outputs, and connecting its React display to Kibana.

Command

Part of the kibana-plugin-helper plugin — 1 skill, 8 commands, 5 agents shipped together

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 commands/ch-bas/kibana-plugin-helper/embeddable
Clone the repo
git clone --depth 1 https://github.com/ch-bas/kibana-plugin-helper

Or install kibana-plugin-helper, the plugin that ships this one along with the rest of its 1 skill, 8 commands, 5 agents.

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,191 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00028 $0.01191
Opus 5 $0.00014 $0.00596
Sonnet 5 $0.00006 $0.00238
Haiku 4.5 $0.00003 $0.00119

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

Security

Grade A, and why

embeddable 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 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.

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.

commands/embeddable.md · 104 lines

How it starts

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

Generate Kibana Embeddable

Create a custom Embeddable that can be rendered inside Kibana Dashboards or other container contexts. Ask the user for:

  1. Embeddable type ID (snake_case, e.g. my_plugin_widget)
  2. Display name (human-readable, e.g. "My Plugin Widget")
  3. What it renders (description of the visualization or content)
  4. Input parameters (what data/config the embeddable accepts from the dashboard)
  5. Output parameters (what data the embeddable exposes to the dashboard/container)
  6. Data source: Does it query Elasticsearch directly, use a saved object, or receive all data via input?
  7. Interactive? Does it emit events (e.g. filter clicks, drilldowns)?
  8. Needs saved object reference? Can users save/load configurations for this embeddable?

Generation Steps

  1. Create the embeddable directory structure:

    public/embeddable/
    ├── index.ts
    ├── my_embeddable.tsx           # The embeddable class
    ├── my_embeddable_factory.ts    # Factory for creating instances
    ├── my_embeddable_component.tsx # React component rendered inside
    └── types.ts                    # Input/Output interfaces
    
  2. Define Input and Output interfaces in types.ts:

    • Input extends EmbeddableInput — includes id, title, timeRange, filters, query, plus custom fields
    • Output extends EmbeddableOutput — includes any data the embeddable exposes to the container
  3. Create the Embeddable class:

    • Extends Embeddable<MyInput, MyOutput>
    • Implements render(node: HTMLElement) and reload() methods
    • Renders a React component into the provided DOM node
    • Handles input changes via this.getInput() and this.updateInput()
    • Handles output updates via this.updateOutput()
    • Implements destroy() for cleanup (unmount React, cancel subscriptions)
  4. Create the EmbeddableFactory:

    • Extends EmbeddableFactoryDefinition
    • Sets type, displayName, grouping, getIconType()
    • Implements create(input, parent?) to instantiate the embeddable
    • Optionally implements getExplicitInput() for a creation wizard/modal
    • Optionally implements canCreateNew() and isEditable()

Read the full file on GitHub · 104 lines

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 · 104 lines · 28 tokens per session scan A 1e4f00711608

Subscribe to this mod's changes

embeddable is a command published in the GitHub repository ch-bas/kibana-plugin-helper (3 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 1,191 once invoked, about $0.0001 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-31.