kibana

kibana is a skill for Claude Code from vmkteam/claude-plugins. It costs 44 tokens per session (1,342 once invoked), scanned A, original, MIT.

A guide for searching nginx, infrastructure, and application access logs in Kibana or OpenSearch Dashboards, tools for viewing and querying log data. It explains how to discover available indexes and fields before searching.

In plain words
What is it for?
Finding web-server errors, request records, and infrastructure events through the Elasticsearch or OpenSearch API, including selecting the right index and query fields.
Why use it?
Different log indexes use different field names, and application logs may be stored elsewhere. The discovery steps help prevent searches that silently miss the relevant records.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the vmkteam-developer plugin — 35 skills shipped together

Good fit Finding web-server errors, request records, and infrastructure events through the Elasticsearch or OpenSearch API, including selecting the right index and query fields.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vmkteam/claude-plugins/kibana
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.

Any agent
npx skills add vmkteam/claude-plugins --skill kibana
Clone the repo
git clone --depth 1 https://github.com/vmkteam/claude-plugins

Made for: Claude Code.

Or install vmkteam-developer, the plugin that ships this one along with the rest of its 35 skills.

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

agentmods badge for kibana

README.md
[![agentmods](https://agentmods.dev/badge/skills/vmkteam/claude-plugins/kibana/github.svg)](https://agentmods.dev/skills/vmkteam/claude-plugins/kibana)
Your own site
<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/kibana"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/kibana/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.

agentmods 80×15 button for kibana

Your own site · 80×15
<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/kibana"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/kibana.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,342 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00044 $0.01342
Opus 5.5 $0.00018 $0.00537
Sonnet 5.5 $0.00009 $0.00268
Haiku 4.5 $0.00004 $0.00134

Measured 23d ago against content hash b03c8d96c7a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kibana 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 23d 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.

plugins/developer/skills/kibana/SKILL.md · 99 lines

How it starts

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

Kibana / OpenSearch Dashboards — логи

OpenSearch Dashboards (или Kibana) для поиска по логам (nginx access/error, application). Приложенческие логи Go-сервисов — в Loki (см. /loki).

Разные индексы содержат разные данные от разных систем. Имена полей зависят от индекса. Всегда начинай с discovery.

OpenSearch Dashboards использует заголовок osd-xsrf: true вместо kbn-xsrf: true (Kibana).

Подключение

Profile: @{kibana_profile}
Base URL: https://{kibana_host}
Header: osd-xsrf: true (OpenSearch) или kbn-xsrf: true (Kibana)

Шаг 1. Discovery

Index patterns (рекомендуется — самый надёжный способ)

pcurl @{profile} 'https://{host}/api/saved_objects/_find?type=index-pattern&per_page=100' -s -H 'osd-xsrf: true'

Пример документа — быстрый способ понять структуру полей

pcurl @{profile} 'https://{host}/api/console/proxy?path={index}/_search&method=POST' \
  -s -H 'osd-xsrf: true' -H 'Content-Type: application/json' \
  -d '{"sort":[{"@timestamp":"desc"}],"size":1}'

Mapping индекса (полная структура полей)

pcurl @{profile} 'https://{host}/api/console/proxy?path={index}/_mapping&method=POST' \
  -s -H 'osd-xsrf: true' -H 'Content-Type: application/json' -d '{}'

Типичные index patterns:

  • nginx-access-* — nginx access логи (ip, path, httpStatus, requestTime, serverName, platform, xRequestId)
  • nginx-error-* — nginx error логи (level, description, connectionId)
  • {service}-* — приложенческие логи (если не в Loki)
  • logstash-* — legacy

Шаг 2. Поиск логов

Использовать реальные имена полей из discovery.

# По query string
pcurl @{profile} 'https://{host}/api/console/proxy?path={index}/_search&method=POST' \
  -s -H 'osd-xsrf: true' -H 'Content-Type: application/json' \
  -d '{"query":{"query_string":{"query":"{query}"}},"sort":[{"@timestamp":"desc"}],"size":20}'

# За период
pcurl @{profile} 'https://{host}/api/console/proxy?path={index}/_search&method=POST' \
  -s -H 'osd-xsrf: true' -H 'Content-Type: application/json' \
  -d '{"query":{"bool":{"must":[{"query_string":{"query":"{query}"}},{"range":{"@timestamp":{"gte":"now-1h","lte":"now"}}}]}},"sort":[{"@timestamp":"desc"}],"size":50}'

# Nginx: 5xx ошибки
pcurl @{profile} 'https://{host}/api/console/proxy?path=nginx-access-*/_search&method=POST' \
  -s -H 'osd-xsrf: true' -H 'Content-Type: application/json' \
  -d '{"query":{"bool":{"must":[{"range":{"httpStatus":{"gte":500}}},{"range":{"@timestamp":{"gte":"now-1h"}}}]}},"sort":[{"@timestamp":"desc"}],"size":20}'

# Nginx: медленные запросы
pcurl @{profile} 'https://{host}/api/console/proxy?path=nginx-access-*/_search&method=POST' \
  -s -H 'osd-xsrf: true' -H 'Content-Type: application/json' \
  -d '{"query":{"bool":{"must":[{"range":{"requestTime":{"gte":1}}},{"range":{"@timestamp":{"gte":"now-1h"}}}]}},"sort":[{"requestTime":"desc"}],"size":20}'

# По X-Request-ID (trace)
pcurl @{profile} 'https://{host}/api/console/proxy?path=nginx-access-*/_search&method=POST' \
  -s -H 'osd-xsrf: true' -H 'Content-Type: application/json' \
  -d '{"query":{"term":{"xRequestId":"{request_id}"}},"size":10}'

Read the full file on GitHub · 99 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. 23d ago Changed · +1 lines b03c8d96c7a0
  2. 1mo ago First seen · 98 lines · 44 tokens per session scan A 545bdadd5af8

Subscribe to this mod's changes

kibana is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 6d ago), licensed MIT. It adds 44 tokens to every session and 1,342 once invoked, about $0.0002 per session on Opus 5.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.

Related

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

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…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens