@liustack/modsearch
A free web-search plugin aimed at coding agents.
Version 5.10.12 of @liustack/modsearch, last published 2026-11-07; the install command and the range come from its own manifest.
Install
dsh plugin add @liustack/modsearch writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.
dsh plugin --profile web add @liustack/modsearchCompatibility
@liustack/modsearch ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.
If two plugins fight
Declares no peers and no dsh range, so nothing pre-checks it. It competes with dsh-free-search for the same job; two providers on the same profile is the conflict you will actually notice.
Who made it
Author: liustack. Repository: https://github.com/liustack/modsearch. Package page: https://www.npmjs.com/package/@liustack/modsearch.
After install
It declares no dsh peer and renders a search tool in the tool list; after dsh plugin add @liustack/modsearch, dsh --profile web --dump-config lists the @liustack/modsearch row that mounts it.
Files it touches
No storage peer appears in the manifest of @liustack/modsearch, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.
Removing it
Removing @liustack/modsearch is the mirror command, dsh plugin --profile web remove @liustack/modsearch. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.
Common questions
Does it collide with dsh-free-search?
For @liustack/modsearch the recommendation is dsh-free-search: It peers @deepseek-ai/dsh-tools and the command palette, so the provider is reachable from the UI; modsearch declares no peers at all.
What happens when dsh upgrades?
Nothing declares a version window for @liustack/modsearch: dsh --version tells you what you are running, and no check will tell you whether @liustack/modsearch matches it.