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.
git clone --depth 1 https://github.com/ch-bas/kibana-plugin-helperWrote 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.
[](https://agentmods.dev/commands/ch-bas/kibana-plugin-helper/mcp-config)<a href="https://agentmods.dev/commands/ch-bas/kibana-plugin-helper/mcp-config"><img src="https://agentmods.dev/badge/commands/ch-bas/kibana-plugin-helper/mcp-config.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.00989 |
| Opus 5 | $0.00015 | $0.00495 |
| Sonnet 5 | $0.00006 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
mcp-config 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate MCP Configuration
Set up MCP server connections so Claude Code has live access to your Elasticsearch cluster and Kibana instance while developing plugins. Ask the user for:
-
Which MCP servers? Options:
- Elasticsearch MCP only (recommended minimum)
- Elasticsearch + Kibana MCP (recommended for full-stack plugin dev)
- Elasticsearch + Kibana Agent Builder MCP (for Kibana 9.2+ / Serverless)
-
Elasticsearch connection:
- URL (default:
https://localhost:9200) - Auth method: API key, username/password, or cloud ID
- SSL verification (default: true)
- URL (default:
-
Kibana connection (if selected):
- URL (default:
https://localhost:5601) - Auth method: API key or username/password
- For Agent Builder: Kibana Cloud URL
- URL (default:
-
Docker or local?
- Docker (recommended — no local install needed)
- Local Node.js (for Kibana MCP community server)
-
Scope:
- Project-level (
.mcp.jsonin project root) - Global (
~/.claude/mcp.json)
- Project-level (
Generation Steps
- Collect all connection details
- Generate
.mcp.jsonwith the selected MCP servers - Generate a
.envfile for secrets (if not using env vars already) - Add
.envto.gitignoreif not already present - Test the connection by describing how to verify with
claude /mcp
Important Rules
- Never hardcode API keys or passwords in
.mcp.json— always use environment variable references - Always recommend read-only API keys for development
- Remind the user to add
.envto.gitignore - For Docker-based ES MCP, use
--network hostwhen ES runs on localhost - For the Kibana community MCP server, verify the user has cloned and installed it
- Test connectivity: after generating, tell the user to run
claude /mcpto verify servers are connected - Recommend starting with ES MCP alone — it covers 80% of use cases
Template: ES MCP Only (Docker)
{
"mcpServers": {
"elasticsearch": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"--network", "host",
"-e", "ES_URL",
"-e", "ES_API_KEY",
"docker.elastic.co/mcp/elasticsearch"
],
"env": {
"ES_URL": "${ELASTICSEARCH_URL}",
"ES_API_KEY": "${ELASTICSEARCH_API_KEY}"
}
}
}
}
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.
- 8d ago First seen · 130 lines · 30 tokens per session scan A 4ecf92519490
mcp-config is a command published in the GitHub repository ch-bas/kibana-plugin-helper (3 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 989 once invoked, about $0.0002 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.
Other commands, from other repositories
dead-code-clean
Actively find and remove dead code, unused imports, duplicates, and zombie code.
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
dotnet-harden
Scan and harden .NET backend code against high-impact anti-patterns such as sync-over-async, lifetime bugs, fat endpoints, and fragile SignalR state.
dotnet-teach
One-time setup that scans a .NET backend project, learns its conventions and architecture, and writes them to CLAUDE.md for future sessions.