DSH Marketplace

modsearch

liustack/modsearch

Web search bridge for text-only agents: ask the web or X, get structured JSON evidence (search, fetch, citations).

80928TypeScriptMITSource

Install

Add modsearch to DeepSeek Harness

Install into

via npm

Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.

via GitHub · npm package

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

What happened when we ran it

Installed cleanly when we ran it

Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 11d agoon DeepSeek Harness 0.2.2-rc.1.

Show it in your README

install verified — dshmarketplace

For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.

Due diligence

Before you install modsearch

  • Source of record: liustack/modsearch — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.

Security

What installing modsearch runs

Build scripts

No build script was blocked in our run.

Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 11d ago.

Install hooks

package.json declares no preinstall, install or postinstall script.

Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.

README mentions

shell commands (bash, exec, spawn …)

Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.

Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.

The AI take

What it is — Gives a text-only agent web search, page fetch, and X lookup, returning cited JSON.

Who it is for — You run DeepSeek or GLM in DeepSeek Harness to draft or verify against live pages those models cannot open. If the work already lives in a chat app that ships native web search, this is not aimed at that setup.

Watch out — A clean-profile sandbox install succeeded and DeepSeek Harness registered the plugin. Default is Firecrawl's keyless tier at 1,000 credits per month, then automatic failover; X search needs Grok Build, and Tavily or Exa keys go in ~/.modsearch/config.json. It executes shell commands on the host.

The verdict — I would give it the search slot on a text-only DSH profile and stop there, rather than wiring every engine as part of setup.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What modsearch does

Abstract diagram of scattered web signals converging into structured evidence cards.

modsearch is a DeepSeek Harness plugin that adds web, X, and single-page reading tools for text-only agents. It connects the harness’s built-in web_search to an engine chain, adds x_search and read_page, and returns structured JSON evidence with sources and citations. The available engines are Antigravity CLI, Tavily, Exa, Firecrawl, Grok Build, and the built-in local fetcher; configured engines fail over when one fails or exhausts its quota.

Configuration is stored in ~/.modsearch/config.json with mode 0600. API credentials can be set with modsearch config set tavily.apiKey, modsearch config set exa.apiKey, or modsearch config set firecrawl.apiKey, or supplied through TAVILY_API_KEY, EXA_API_KEY, and FIRECRAWL_API_KEY. The plugin can also use compatible endpoints through each engine’s baseURL setting.

It is intended for agents that need current web evidence, X search, or focused page extraction beyond the harness’s native search. It is a poor fit when existing web_search is sufficient, or when external engine setup is unacceptable: Antigravity CLI needs browser sign-in, X search needs Grok Build with SuperGrok or X Premium, and API engines require quotas or credentials. The terminal surface reaches the host terminal to install or run helper CLIs such as agy and grok, and to run the plugin’s configuration commands.

modsearch documentation

Configuration

modsearch uses an engine chain. The default channel is Antigravity CLI, which is free but requires browser sign-in. API credentials may be stored in ~/.modsearch/config.json with file mode 0600, or supplied through environment variables.

Engine Capability Configuration
Antigravity CLI Web search and page fetch Install agy and sign in
Tavily Web search tavily.apiKey; TAVILY_API_KEY
Exa Web search exa.apiKey; EXA_API_KEY
Firecrawl Web search and page fetch firecrawl.apiKey; FIRECRAWL_API_KEY
Grok Build X search Install grok and sign in
local Page fetch Built in

Each engine can be pointed at a compatible third-party or self-hosted service with its baseURL setting. Multiple configured engines are tried in order, with automatic failover.

Commands

The documented configuration form is modsearch config set <key> <value>, for example modsearch config set tavily.apiKey <key> or modsearch config set tavily.baseURL <url>. The CLI also provides configuration and health-check functions through its config and doctor commands.

How it behaves

The plugin connects the harness’s built-in web_search to the configured engine chain and supplies x_search for X and read_page for focused single-page reading. Results are returned as structured JSON evidence, including sources and citations. A search or fetch can be triggered through conversation when the agent needs current information or a URL read.

Requirements and limits

At least one search-capable engine is needed for web search. Antigravity CLI requires the agy installation and browser sign-in; Grok Build requires a SuperGrok or X Premium account. Tavily, Exa, and Firecrawl use their respective quotas or API-compatible endpoints. local provides page fetching only, so it does not replace a web-search engine.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to modsearch

BrowserSkill bridge for controlling visible Chrome and Edge Agent Windows from DeepSeek Harness, with native browser tools, accessibility and VOM observations, screenshots, owned multi-session control, and a live Web UI overlay.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScripttoday

AI review

dsh-plugin-browserskill

What it is — The BrowserSkill plugin bridges DeepSeek Harness to control visible Chrome and Edge agent windows, with native browser tools, accessibility and VOM observations, screenshots, and multi-session management.

Who it is for — This plugin suits agents using DeepSeek Harness to handle tasks like page summarization or form interactions on logged-in websites. It is unnecessary for agents focused only on local code generation without browser requirements.

Watch out — It must be installed as a subdirectory plugin for DeepSeek Harness. Static checks indicate capability to execute shell commands. No obvious issues identified, as sandbox testing has not been performed.

The verdict — I would install it because it enables visible agent windows for browser tasks, allowing continued personal browser use without interruption.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source
833

Chrome sidebar extension that lets DSH operate your browser directly, no vision capabilities required.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScript1mo ago

AI review

bridge-browser

What it is — bridge-browser enables DeepSeek Harness to directly operate your open Chrome or Firefox tabs, with the model able to read page content, control elements, and manage tabs via a sidebar conversation interface.

Who it is for — Users who need to automate web tasks using DeepSeek Harness with deepseek-v4-flash and want to preserve browser login states would benefit if they lack browser control capabilities. Users who do not want to provide an API key or token can choose other approaches.

Watch out — No obvious pitfalls were found. It requires providing an API key or token. The plugin will execute shell commands.

The verdict — I would install it because it can reduce tool calls and lower latency compared to the Playwright baseline.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
2Source
809

Chrome sidebar extension that lets DSH operate your browser directly, no vision capabilities required.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScript1mo ago

AI review

bridge-browser

What it is — bridge-browser is a DeepSeek Harness browser control plugin that allows the model to directly operate your existing browser without vision capabilities required.

Who it is for — When you use DeepSeek Harness to perform browser tasks such as clicking, form filling and navigation, you need browser control capabilities. If your work does not require preserving session state in the browser, you do not need to install this plugin.

Watch out — Installing this plugin requires Node.js ^22.19 or >=24 version. It requires Chrome 116+ or Firefox 140+. No obvious issues found.

The verdict — If I need to perform browser tasks in DeepSeek Harness, I would install it because it requires fewer model and tool round trips and finishes tasks faster.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
2Source

Free, keyless web search for DSH: 7 engines (DuckDuckGo/Bing/SearXNG free + Exa/Perplexity/DeepSeek paid), auto-failover, settings-page UI with API key inputs and official links, web_fetch, and an engine test tool.

Installed cleanly when we ran it

npm packageJavaScript1mo ago

AI review

dsh-free-search

What it is — dsh-free-search adds multi-engine web_search tools to DeepSeek Harness, supporting engine switching and testing.

Who it is for — It is suitable when your agent uses gateways that do not support the web_search tool. Users who do not need web search capabilities are not suitable for this plugin.

Watch out — Sandbox testing confirmed successful installation in fresh profile and registration with harness, no obvious issues found.

The verdict — I would install it because it provides a keyless search option, but only if the agent requires web search tools.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
2Details

Drive a real Chrome/Chromium browser from DeepSeek Harness with 35 structured tools for navigation, snapshots, clicks, forms, JavaScript/CDP, screenshots, downloads and tabs; a live sidebar mirrors the page and accepts mouse and keyboard input. It ships a managed CDP runtime, keeps login state across calls, and can import cookies from your everyday Chrome through a companion extension.

Installed cleanly when we ran it

npm packageTypeScript13d ago

AI review

dsh-ego-browser

What it is — DeepSeek Harness integrates this plugin to drive real Chrome browser with real-time sidebar observation.

Who it is for — When the DeepSeek Harness agent needs to perform webpage navigation and form operations, this plugin provides real-time browser observation. If the project does not use DSH desktop, users need not install it because it relies on DSH native right sidebar for panel support.

Watch out — Sandbox testing passed: installed in a new profile and registered into the profile by harness. No obvious pitfalls found.

The verdict — I would install it because it supports importing login states from everyday Chrome and keeping them across calls.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details
144

Shared real browser for DSH: a native Electron window the human can watch and take over, driven by the agent over CDP with 20 browser_* tools (open/snapshot/execute/fill/screenshot/download/auth), per-task session isolation, cookie persistence, CAPTCHA detection; self-hosts on plain dsh web without a desktop shell.

Installed cleanly when we ran it

npm packageJavaScript23d ago

AI review

dsh-browser

What it is — Adds shared real browser plugin for DeepSeek Harness, enabling agent to drive visible native Electron window shared with humans for observation and takeover.

Who it is for — When performing web automation tasks with DeepSeek Harness agent that require human oversight, this plugin is suitable to install. If your tasks do not involve visible browser control, using headless solutions is sufficient.

Watch out — No obvious issues found. Sandbox test passed: installed in new profile and registered into profile. Self-hosts in plain dsh web environment without desktop shell.

The verdict — I will install it because it self-hosts on plain dsh web without requiring a desktop shell.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Source