DSH Marketplace

argo

taxueseek/argo

Search built for agents: multilingual coverage across web, academic, code, shopping, finance, news, and encyclopedias.

20514PythonApache-2.0Source

Install

Add argo 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 argo

  • Source of record: taxueseek/argo — present in the community registry that DSH's own plugin market installs from.
  • Licensed under Apache-2.0.

Security

What installing argo 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 — Argo is a multilingual search infrastructure designed for AI agents.

Who it is for — When building agents with DeepSeek Harness to handle stock queries, movie information, or geography queries, Argo can directly provide answer results, which helps agents lacking native search capabilities. If you only want model built-in search outputs and don't care about evidence scoring and caching mechanisms, you don't need to install Argo.

Watch out — Sandbox test passed with installation in a new profile and registration by harness. No obvious pit found. It will execute shell commands.

The verdict — I would install it because it supports a budget mode prioritizing free engines with optional keys.

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 argo does

Multilingual query streams route through search engines, converge, and condense into a cached evidence block.

argo is a DeepSeek Harness plugin that provides multilingual search and evidence-oriented results for web, academic, code, shopping, finance, news and encyclopaedia queries. It is intended for agents that need compact, sortable material rather than a long generated answer or an unstructured list of links.

The plugin exposes Argo through MCP, providing 10 mcp__argo__* tools. A query can pass through language detection, domain routing, multiple search engines, RRF result fusion and a fast evidence review. The returned JSON includes fields such as selection, absorption, freshness, credibility_fast, evidence_flags, engine_outcomes and recovery. Argo also supports search.py for command-line use, mcp_server.py as a local Python MCP entry point, and local file search. It uses an in-memory and SQLite cache; configuration is read with PyYAML.

This plugin is for research, fact checking and domain-specific retrieval where language and source choice matter. It is a poor fit when only a simple search command is needed, or when browser rendering, screenshots or PDF extraction are required without their optional dependencies. Python 3.10+ is required, and API keys are optional rather than guaranteed for every source. With the listed terminal-surface risk, the plugin reaches the agent’s terminal to run its Python scripts, MCP server and optional local search tools; that access supports command-line and local-file search, but should be considered when granting it to an agent.

argo documentation

How it behaves

Argo routes each query using language detection, domain rules, TF-IDF, budget and cached hot paths. It can query several engines in parallel, combine results with RRF, optionally rerank them, and perform a fast evidence review. Empty results can trigger staged recovery: widening the query, switching to a related or general engine, and then trying another language. Results are returned as compact JSON, with engine_outcomes and recovery included when applicable.

The evidence fields are intended for agent-side sorting. selection reflects source authority, absorption reflects evidence density, and freshness reflects publication timing. The README recommends search followed by fetch for high-consequence questions, and advises treating search-result pages, redirect chains and social posts cautiously.

Commands and entry points

Entry point Purpose
scripts/search.py "query" --json Run a JSON search from the command line
scripts/search.py --list-engines List available engines
scripts/mcp_server.py Start the local Python MCP server
npx -y github:taxueseek/argo Start the GitHub MCP entry point
from search import super_search Call the library from Python

The DSH bundle is under packages/dsh-plugin/. A user-level cordis.patch.yml can override the mcp-argo source.

Configuration

PyYAML reads the configuration files. API keys are optional: without them, Argo uses free engines and local local_* engines, while configured sources can provide additional coverage. The optional environment variable ARGO_PYTHON selects the Python executable for the npx entry point.

Requirements

Python 3.10+ and PyYAML are required. Node.js 18+ is needed for the npx MCP route. curl_cffi, ddgs CLI, realtime-index CLI, Chrome, pdfplumber, PyMuPDF and Playwright are optional. They add browser-TLS handling, local search backends, real-time indexing, rendering or screenshots, and PDF extraction.

Known limits

Without optional dependencies, the related engine or tool is disabled or falls back as documented. In particular, argo_pdf requires a PDF extractor, and screenshot support requires Chrome or Playwright. The README does not name individual API-key configuration keys.

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 argo

38k

Four read-only tools over a WeKnora knowledge base: list knowledge bases, hybrid passage search, reassemble one document's chunks in order, and WeKnora's own cited RAG or ReAct-agent answer with a resumable session id.

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

GitHub sourceGoyesterday

AI review

dsh-weknora

What it is — dsh-weknora provides four read-only tools to operate WeKnora knowledge base for DeepSeek Harness.

Who it is for — When using ReAct-agent in DeepSeek Harness to process WeKnora knowledge base, these tools can provide corresponding capabilities. If you do not use DeepSeek Harness for agent tool calls but rely on other integration methods, you do not need this plugin.

Watch out — Needs to provide API key or token. Will execute shell commands. No obvious pitfalls found.

The verdict — I will install it because it provides WeKnora knowledge base's RAG or ReAct-agent answer function.

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

treg

superdesigndev

6.0k

Tool catalog for agents: search ~2,600 external endpoints (SEO and SERP, backlinks, social, people and company enrichment, ad libraries, scraping) by the task you want done, read each one's parameters and per-call price, then call it with the credential injected server-side. Ships the skill plus an MCP row that stays disabled until TREG_TOKEN is set.

Installed cleanly when we ran it

GitHub sourcePython24d ago

AI review

treg

What it is — Lets an agent find external endpoints by the job to be done, read params and per-call price, then invoke them with credentials injected server-side.

Who it is for — You are in DeepSeek Harness pulling backlinks, SERP, social, or company enrichment without Semrush-class seats. Skip it if secrets must stay on the caller host, or the environment cannot send traffic to an outside proxy.

Watch out — A clean-profile install completed and the harness registered the plugin. MCP stays disabled until TREG_TOKEN is set, and setup or runtime will run shell. Catalog usage is billed per call; newly verified accounts get a one-time $1.00.

The verdict — Skill is enough to shop the catalog. MCP stays off on my machine until the team is actually routing its own CLIs and skills through the same proxy.

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

dsh-ops

T-Auto

5.3k

Provides bash, PowerShell 7, and high-performance Rust tools for DSH on Windows to reduce token usage.

DeepSeek Harness 0.2.2-rc.1 refuses the latest release

npm packageJavaScript11d ago

AI review

dsh-ops

What it is — An ops layer for DSH: extra bash, PowerShell 7, and Rust-backed tools, optional stock-Shell hiding, and on-demand loading so tool traffic stays small.

Who it is for — You are in Native or PTC on DeepSeek Harness, grinding bulk file edits or pdf and word reads, and oversized dumps plus error loops are chewing rounds. If the bill is almost all long reasoning with barely any tool calls, swapping this surface will not move cost.

Watch out — DeepSeek Harness 0.2.2-rc.1 rejects the newest release before install because the declared dsh range omits that version; 0.4.1 installed on the same host. The docs name 0.2.0-rc.2 and 0.2.1-rc.2 as supported hosts. It executes shell commands as part of the job.

The verdict — I would add it pinned to 0.4.1, or let dshmarketplace-cli choose—not latest.

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

dsh-blender-plugin

sixtysevenlf

1.5k

Lets a DSH agent drive a local Blender over a direct TCP channel with 15 tools: viewport frames, custom-angle renders, Python execution, headless and job offload, transaction rollback, and a planning layer of 228 ops across 34 families.

Installs, but needs a build approved first

GitHub sourcePython18d ago

AI review

dsh-blender-plugin

What it is — Hooks a DSH agent into a live local Blender session over TCP, exposing 15 tools plus a 228-op planning layer.

Who it is for — You already run a DSH agent on a machine with Blender 4.x or 5.x—lofting, measuring a reference image, or auditing an assembly—and it still cannot grab a viewport frame or execute Python in that session. If your 3D path never attaches to a local Blender process, there is no session to drive.

Watch out — The sandbox got the package in, then pnpm blocked the build script and Harness never finished registration until that build was allowed by hand. The bundled Blender addon must be enabled first, with Node.js 20+ and Blender 4.x or 5.x. It executes shell commands.

The verdict — Worth it only on a box that already has Blender to connect; I would allow the blocked build first rather than chase a registration that never ran.

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
1.4k

Anime Garden for DSH: search anime torrent resources from 動漫花園, 蜜柑计划, 萌番组 and ANi inside DSH — via chat, a sidebar panel with fansub and type filters, a seasonal calendar, and an in-app floating player.

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

GitHub sourceTypeScript13d ago

AI review

AnimeGarden

What it is — Brings anime torrents from 動漫花園, 蜜柑计划, 萌番组, and ANi into DSH, searchable in chat or a sidebar, plus a season calendar and a floating player.

Who it is for — You are inside a DeepSeek Harness agent picking this season’s release and still leave the session to filter by fansub and type. If MCP or the HTTP API already feeds that index in another toolchain, skip this plugin.

Watch out — This listing has no one-line install; the plugin lives in a repo subdirectory and has to be wired in by hand. It runs shell commands. No sandbox run is on record, so there are no measured pitfalls.

The verdict — I’d add it only if torrent hunting already happens inside DSH most weeks.

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

dsh-plugin

TencentCloudBase

1.2k

Tencent CloudBase backend for DeepSeek Harness — scaffold and deploy full-stack apps from chat, render query results as table cards with paging, sorting and CSV export, preview a deployment on its domain, and call the CloudBase MCP toolset (`mcp__cloudbase__*`) with device-code login.

Installed cleanly when we ran it

npm packageTypeScript2d ago

AI review

dsh-plugin

What it is — A DeepSeek Harness plugin that drives Tencent CloudBase from the thread: scaffold and deploy full-stack apps, present query results as table cards with paging, sorting and CSV export, preview a release on its domain, and call CloudBase MCP tools after device-code login.

Who it is for — You are shipping a full-stack app from DeepSeek Harness onto Tencent CloudBase and still lack an in-thread MCP bridge plus a DB / Storage / Auth panel. If CloudBase is not the runtime, this is the wrong door; if the Toolkit already lives in another AI IDE and DeepSeek Harness is only a second editor, the gap is not this plugin.

Watch out — On a fresh profile the sandbox install completed and DeepSeek Harness registered it. You still bring the CloudBase environment; login is device-code; shell commands run at runtime. Sensitive actions the agent proposes still need a human yes—the Toolkit does not supply judgment.

The verdict — A clean install is not a reason to add it; I would keep it only when query and release are actually supposed to happen in the DSH thread.

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