modsearch@5.10.14
CAUTION· install onlyPublisher claims: "The strongest free web search plugin for coding agents. Plug-in web search, X search, and page fetch for models without native web access. Free out of the box: no signup, no API key (Firecrawl keyless, 1,000 free credits/month)" Observed in sandbox: reads credential files.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 4 of 4 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 5.10.12
vet-skills diff modsearch 5.10.12 5.10.14This version reaches for something 5.10.12 did not: 1 new credential file (~/.npmrc). Compared from the two recorded runs, not from source.
- New credential files
- ~/.npmrc
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Pipe-to-shell pattern; Image alt text carrying instructions; Pipe-to-shell pattern. Summary: reads credential files.
Behavior trace
Honeypot run · 1 s · 2 scenariosStatic findings
'Run `npx @liustack/modsearch doctor` in a terminal to check the engine setup.',Fix: Pin versions and sources; vendor anything fetched at install time.const INSTALL_GROK = "curl -fsSL https://x.ai/cli/install.sh | bash && grok";Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…ns X itself was unreachable and a keyless web search answered second-hand. Run `npx @liustack/modsearch doctor` to inspect the resolved engines.', parameters: { type: 'objec…Fix: Pin versions and sources; vendor anything fetched at install time.const INSTALL_AGY = "curl -fsSL https://antigravity.google/cli/install.sh | bash && agy";Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.if command -v npx >/dev/null 2>&1 && node_meets_floor; thenFix: Pin versions and sources; vendor anything fetched at install time.The ModSearch page in the dsh Plugins panel, shown in Chinese: pick the preferred engine, fill in an API key and endpoint, tick the engines that join failoverFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.2. Otherwise, if `npx` exists: `npx --yes --package @liustack/[email protected] modsearch <args>`.Fix: Pin versions and sources; vendor anything fetched at install time.const INSTALL_GROK = "curl -fsSL https://x.ai/cli/install.sh | bash && grok";Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# node itself meets the CLI's floor. An old node with a working npx used to beFix: Pin versions and sources; vendor anything fetched at install time.const INSTALL_AGY = "curl -fsSL https://antigravity.google/cli/install.sh | bash && agy";Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…ode. Private-network URLs are blocked. Page reading needs no engine setup. Run `npx @liustack/modsearch doctor` to inspect the resolved route.', parameters: { type: 'object'…Fix: Pin versions and sources; vendor anything fetched at install time.# 2. npx present -> run the pinned npm version.Fix: Pin versions and sources; vendor anything fetched at install time....permissionsOk ? {} : { note: `group/world can read this file. Run: chmod 600 ${configPath}` },Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.# The npx path runs the CLI on this machine's node, so npx is only usable whenFix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for @liustack/modsearch@5.10.14 as of 7 min ago. This is the package itself, not its dependencies.
What would make this Verified
15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Reads credential files≈ +27 on the totalThe sandbox saw reads under ~/.ssh, ~/.aws, ~/.npmrc, ~/.config or similar. Read only files inside the project, and only the ones the task needs. Seen: ~/.npmrc.
- Pipe-to-shell pattern≈ +9 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Unclaimed publisher≈ +8 on the totalClaim liustack: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.