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/fprochazka/claude-code-plugins/searxngclinpx skills add fprochazka/claude-code-plugins --skill searxngcligit clone --depth 1 https://github.com/fprochazka/claude-code-pluginsWhat 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.00080 | $0.00990 |
| Opus 5 | $0.00040 | $0.00495 |
| Sonnet 5 | $0.00016 | $0.00198 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
searxngcli 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 2d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
searxngcli
Search the web via a private SearXNG metasearch engine instance using the searxng CLI.
SearXNG aggregates results from multiple search engines (Google, Bing, DuckDuckGo, etc.) and supports engine-specific operators like site:, filetype:, intitle: — these are passed through to backend engines as-is.
Usage
Always use --json for machine-readable output. Always quote the query string.
# Basic search
searxng search "python asyncio" --json
# Filter by category (general, images, news, videos, music, files, it, science, social media)
searxng search "breaking news" --categories news --json
# Filter by specific engines
searxng search "rust" --engines google,duckduckgo --json
# Filter by time range (day, week, month, year)
searxng search "latest updates" --time-range week --json
# Combine filters
searxng search "climate change" --categories news --time-range month --num 20 --json
# Use search engine operators (passed through to engines)
searxng search "site:github.com python cli" --json
Search Options
| Flag | Description |
|---|---|
--categories |
Comma-separated categories |
--engines |
Comma-separated engines |
--language |
Language code (en, de, cs, etc.) |
--num |
Number of results (default: 10) |
--page |
Page number (default: 1) |
--time-range |
day, week, month, year |
--safe-search |
0=off, 1=moderate, 2=strict |
--json |
Raw JSON output |
Discovery
# List available engines on the instance
searxng engines
# List available categories
searxng categories
Output Format
The --json output is a JSON object with these top-level fields:
{
"query": "search terms",
"number_of_results": 100,
"results": [
{
"title": "asyncio — Asynchronous I/O — Python 3.14.3 documentation",
"url": "https://docs.python.org/3/library/asyncio.html",
"content": "asyncio is a library to write concurrent code using the async/await syntax...",
"engine": "google",
"engines": ["braveapi", "google", "startpage"],
"category": "general",
"score": 9.0,
"published_date": "2025-07-30T00:00:00",
"thumbnail": ""
}
],
"suggestions": ["related query 1", "related query 2"],
"corrections": []
}
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.
- 2d ago First seen · 103 lines · 80 tokens per session scan A 32376e5c8c0b
searxngcli is a skill published in the GitHub repository fprochazka/claude-code-plugins (11 stars, last pushed 5d ago), licensed MIT. It adds 80 tokens to every session and 990 once invoked, about $0.0004 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-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…