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 skills add automateyournetwork/netclaw --skill elasticsearch-logsgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/elasticsearch-logs)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/elasticsearch-logs"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/elasticsearch-logs/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.
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/elasticsearch-logs"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/elasticsearch-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00101 | $0.01487 |
| Opus 5 | $0.00051 | $0.00744 |
| Sonnet 5 | $0.00020 | $0.00297 |
| Haiku 4.5 | $0.00010 | $0.00149 |
Grade A, and why
elasticsearch-logs 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 9d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elasticsearch Logs
Read-only log search over an Elasticsearch cluster you already run. NetClaw installs no cluster and indexes nothing — this queries what is already there.
Server: elasticsearch-mcp (adopted, docker.elastic.co/mcp/elasticsearch, Apache-2.0,
digest-pinned) · 5 tools · 1,094 tokens
The rule that matters most
A bare
searchtotal is capped at 10,000 and reads as if it were exact.
Elasticsearch stops counting at 10,000 and marks the total relation: "gte" — meaning at
least. This server discards that qualifier and prints Total results: 10000. There is
nothing in the response to tell you the number is a floor.
Measured against 10,075 real documents:
| How you ask | What you get |
|---|---|
search with no guard |
Total results: 10000 — wrong |
search with "track_total_hits": true |
Total results: 10075 — correct |
esql STATS COUNT(*) |
10075 — correct |
On a million-document index a bare search still says 10,000. The error is unbounded and invisible.
Therefore, for any question of the form "how many", "how often", "which is most", or any number a human will act on:
- Use
esqlwithSTATS COUNT(*), or - Use
searchwith"track_total_hits": truein thequery_body.
search without that guard is for retrieving example documents only — never for counting.
If you report a total that came from an unguarded search, you are reporting a number that may
be arbitrarily wrong.
Tools
| Tool | Use it for | Required arguments |
|---|---|---|
list_indices |
what indices exist, and their document counts | index_pattern (use *) |
get_mappings |
field names and types before writing a query | index |
search |
retrieving matching documents (Query DSL) | index, query_body |
esql |
counting, aggregating, grouping, ranking | query |
get_shards |
shard health when results look incomplete | — |
Note the argument names are snake_case (query_body, index_pattern). Wrong names fail
loudly with a deserialization error — they are not silently ignored.
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.
- 9d ago First seen · 136 lines · 101 tokens per session scan A 0d9ab369981d
elasticsearch-logs is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 101 tokens to every session and 1,487 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…