Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/useorgx/orgx-deepseek-harness-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/useorgx/orgx-deepseek-harness-plugin/deepseek-harness-plugin)<a href="https://agentmods.dev/mcp/useorgx/orgx-deepseek-harness-plugin/deepseek-harness-plugin"><img src="https://agentmods.dev/badge/mcp/useorgx/orgx-deepseek-harness-plugin/deepseek-harness-plugin/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/useorgx/orgx-deepseek-harness-plugin/deepseek-harness-plugin"><img src="https://agentmods.dev/badge/mcp/useorgx/orgx-deepseek-harness-plugin/deepseek-harness-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deepseek-harness-plugin scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "deepseek-harness-plugin": { "command": "npx", "args": [ "-y", "@useorgx/deepseek-harness-plugin" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 2da5fd2438ec
deepseek-harness-plugin is an MCP server published in the GitHub repository useorgx/orgx-deepseek-harness-plugin (0 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
opencode-eyes
MCP server "opencode-eyes" as configured in bauerelizabeth07139/opencode-eyes. Runs locally from the opencode-eyes Python package.
repogate
Reusable repository structure baselines for architecture-aware pull request gates. Runs locally from the repogate npm package.
guarftrain
Training Guardian — sidecar training monitor with crash recovery, agent decisions, MCP & web dashboard. Runs locally from the guarftrain Python package.
gpt-dsh-bridge
MCP server "gpt-dsh-bridge" as configured in baochaofan0404/gpt-dsh-bridge. Runs locally from the gpt-dsh-bridge npm package.
dsh-mediacrawler
MCP server "dsh-mediacrawler" as configured in xwh-01/dsh-mediacrawler. Runs locally from the dsh-mediacrawler Python package.
dsh-feed
A local index that combines GitHub data about the dsh-plugin topic with npm registry data. It can be queried by agent tools, a command-line program, or an MCP server.