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/fisker086/aiops/es_querynpx skills add fisker086/AIOps --skill es_querygit clone --depth 1 https://github.com/fisker086/AIOpsWrote 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/skills/fisker086/aiops/es_query)<a href="https://agentmods.dev/skills/fisker086/aiops/es_query"><img src="https://agentmods.dev/badge/skills/fisker086/aiops/es_query.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 | $0.00000 | $0.00384 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
elasticsearch-query 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 4d 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.
What it actually says
Elasticsearch Query Skill
Provides Elasticsearch operations for querying and managing indices:
- search: Execute search queries with ES query DSL
- count: Get document count for index
- mapping: Get index mapping definition
- indices: List all indices
- cluster_health: Get cluster health status
- aliases: List all aliases
Use builtin_es_query tool with fields:
operation: Operation name (search, count, mapping, indices, cluster_health, aliases)addresses: ES addresses (comma-separated, e.g., localhost:9200)index: Index name to queryusername: (optional) ES usernamepassword: (optional) ES passwordapi_key: (optional) ES API key (alternative to username/password)query: ES query JSON (for search/count)size: Number of results (default: 10)_source: Fields to return (comma-separated)timeout: Request timeout in seconds (default: 30)
Example - search:
operation: "search"
addresses: "localhost:9200"
index: "my-logs"
query: "{\"query\": {\"match\": {\"level\": \"error\"}}}"
size: "20"
Example - indices:
operation: "indices"
addresses: "localhost:9200"
Example - cluster health:
operation: "cluster_health"
addresses: "es-node1:9200,es-node2:9200"
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.
- 4d ago First seen · 49 lines · 0 tokens per session scan A fc7d1b61c8a7
elasticsearch-query is a skill published in the GitHub repository fisker086/AIOps (22 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 384 tokens. 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…