ModSearch, Search & Fetch Bridge Skill

Use this skill when:

• The user asks about anything after your knowledge cutoff (releases, news, prices, versions)
• The answer needs source links or verifiable external facts
• The user asks what people are saying on X or Twitter (推特, 推文, tweets, threads)
• The user gives a URL to read and the harness has no fetch tool
• The user asks how to configure modsearch, add a key, or change engines

Do not use this skill for:

• Analyzing images (that is modlens)
• Questions your own knowledge answers reliably and time does not affect
• Searching inside DeepSeek Harness (dsh, DSH_SHELL=1): there modsearch runs as a plugin behind the native web_search. If dsh still answers from its default provider, the plugin is missing: point the user to Step 0 of INSTALL.md

Prerequisites

Run every modsearch command through the launcher bundled with this skill. Replace <skill-dir> with the directory this SKILL.md lives in:

bash <skill-dir>/scripts/run.sh -q "test"                                       # macOS / Linux
powershell -ExecutionPolicy Bypass -File <skill-dir>\scripts\run.ps1 -q "test"  # Windows

The launcher finds a working way to run modsearch and forwards your arguments to it unchanged. It tries, in order: a compatible modsearch already on PATH, then npx, then bunx. If none of those exists it prints a JSON diagnosis to stderr and exits 78, with a nextSteps list for the user. Relay those steps instead of retrying. To see the full diagnosis, run bash <skill-dir>/scripts/run.sh doctor --json (on a machine that can launch the CLI it also chains modsearch's own engine/config doctor).

Nothing else needs setting up first: modsearch works with no config file. Web search and page fetch run out of the box on Firecrawl's keyless free quota (no signup, no key), and a configured engine or API key takes precedence when present.

If you cannot run the launcher script