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/polarskicpl/dsh-codex-migrateWrote 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/polarskicpl/dsh-codex-migrate/dsh-codex-bridge-dshcodexbridge)<a href="https://agentmods.dev/mcp/polarskicpl/dsh-codex-migrate/dsh-codex-bridge-dshcodexbridge"><img src="https://agentmods.dev/badge/mcp/polarskicpl/dsh-codex-migrate/dsh-codex-bridge-dshcodexbridge.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
dshCodexBridge 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 8d 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
{
"dshCodexBridge": {
"title": "DSH Codex Migration",
"description": "Import Codex tasks into DeepSeek Harness and manage local persistent memory.",
"cwd": ".",
"command": "node",
"args": [
"./mcp/server.mjs",
"--stdio"
],
"env_vars": [
"DSH_CODEX_BRIDGE_PORT",
"DSH_CODEX_BRIDGE_STATE",
"DSH_CODEX_BRIDGE_TOKEN_FILE",
"DSH_CODEX_BRIDGE_MEMORY_FILE",
"HOME",
"USERPROFILE",
"LOCALAPPDATA"
],
"startup_timeout_sec": 10,
"tool_timeout_sec": 30
}
}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.
- 8d ago First seen · 23 lines scan A 0afb38551aa6
dshCodexBridge is an MCP server published in the GitHub repository polarskicpl/dsh-codex-migrate (5 stars, last pushed 10d 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
dsh-narrative-ledger
MCP server "dsh-narrative-ledger" as configured in dongsheng123132/dsh-narrative-ledger. Runs ./mcp-server.mjs with node.
url-manager-mcp
URL Manager MCP Server — Agent-first web link collection & knowledge management. Runs locally from the url-manager-mcp Python package. Needs 2 environment variables to run.
dsh-mediacrawler
MCP server "dsh-mediacrawler" as configured in xwh-01/dsh-mediacrawler. Runs locally from the dsh-mediacrawler Python package.
dsh-artifact-promotion-proof
MCP server "dsh-artifact-promotion-proof" as configured in dongsheng123132/dsh-artifact-promotion-proof. Runs ${PLUGIN_ROOT}/mcp-server.mjs with node.
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.
deepseek-visionary
MCP server "deepseek-visionary" as configured in xlight/deepseek-visionary. Launched with https://github.com/xlight/deepseek-visionary/releases/download/v0.2.2/visionary-.