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/HazenSun/dsh-codex-bridgeWrote 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/hazensun/dsh-codex-bridge/dsh-codex-bridge-dsh-codex-bridge)<a href="https://agentmods.dev/mcp/hazensun/dsh-codex-bridge/dsh-codex-bridge-dsh-codex-bridge"><img src="https://agentmods.dev/badge/mcp/hazensun/dsh-codex-bridge/dsh-codex-bridge-dsh-codex-bridge/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/hazensun/dsh-codex-bridge/dsh-codex-bridge-dsh-codex-bridge"><img src="https://agentmods.dev/badge/mcp/hazensun/dsh-codex-bridge/dsh-codex-bridge-dsh-codex-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dsh-codex-bridge 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 9d 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
{
"dsh-codex-bridge": {
"command": "dsh",
"args": [
"--profile",
"codex-bridge"
],
"env": {
"DSH_TELEMETRY_DISABLED": "1"
}
}
}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.
- 9d ago First seen · 12 lines scan A 3c17af579e2c
dsh-codex-bridge is an MCP server published in the GitHub repository HazenSun/dsh-codex-bridge (1 stars, last pushed 5d ago), licensed Apache-2.0. 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
broker
MCP server "broker" as configured in Utopia-V/mixagents. Runs dist/server.js 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-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.
sitepulsar
MCP server "sitepulsar", hosted remotely at mcp.sitepulsar.ai, as configured in SitePulsar/mcp-server.
netid
MCP server "netid" as configured in route6me/mcp. Runs in Docker (docker.io/route6me/netid:1.2.4).
db-semantic-mcp
A multi-backend MCP server (PostgreSQL + SQL Server) for AI coding agents — schema metadata + semantic search. Runs locally from the db-semantic-mcp Python package.