Borrowing it
Nothing to install: this file belongs to linuxfoundation/lfx-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/linuxfoundation/lfx-mcp/main/.agents/skills/validate-search-filters/SKILL.mdgit clone --depth 1 https://github.com/linuxfoundation/lfx-mcpWrote 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/linuxfoundation/lfx-mcp/validate-search-filters)<a href="https://agentmods.dev/skills/linuxfoundation/lfx-mcp/validate-search-filters"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-mcp/validate-search-filters.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.00048 | $0.03937 |
| Opus 5 | $0.00024 | $0.01969 |
| Sonnet 5 | $0.00010 | $0.00787 |
| Haiku 4.5 | $0.00005 | $0.00394 |
Grade A, and why
validate-search-filters scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl` queries must be run via `kubectl exec` into the NATS box pod. How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Search Filters
Validate every filter parameter across all tools that use the query service SDK
in internal/tools/ against the live OpenSearch resources index and the
upstream indexer-contract documentation. Produce a per-filter verdict table
and optionally apply fixes.
Gotchas
- The OpenSearch cluster is AWS-managed and not port-forward accessible. All
curlqueries must be run viakubectl execinto the NATS box pod. - Discover the pod name dynamically — never hardcode it. Use the label
selector
app.kubernetes.io/component=nats-box,app.kubernetes.io/instance=lfx-platformin namespacelfx. - Discover the OpenSearch URL dynamically from the indexer deployment env var
OPENSEARCH_URL. The index name is inOPENSEARCH_INDEX(currentlyresources). Combine them intoOPENSEARCH_BASEURLas shown in Step 1. tagsentries may have empty values (e.g."committee_uid:","project_uid:") — these are indexed but useless for filtering. A tag key is only valid evidence when at least one document has a non-empty value for it.- Mixed old/new data means partial
parent_refscoverage is expected on some resource types. A non-zero hit count on a prefix query is sufficient evidence that the mechanism works. payload.Parentin the query service is a single string. A tool that accepts bothproject_uidandcommittee_uidcan only send one at a time.handleSearchPastMeetingParticipantsandhandleSearchPastMeetingSummariesare dedicated handlers — each owns its own filter logic independently.- Prefer count-only queries over random sampling. A handful of random
documents proves nothing — you can get lucky and see the right fields while
90% of the corpus has them missing. Always run
"size": 0prefix count queries first. Only pull sample documents ("size": 3) as a secondary debugging aid when a count is zero or surprising (e.g. to understand what fields are actually present on that resource type).
Step 1 — Discover infrastructure
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.
- 7d ago First seen · 291 lines · 48 tokens per session scan A e598b85d8692
validate-search-filters is a skill published in the GitHub repository linuxfoundation/lfx-mcp (20 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 3,937 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.