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.
npx skills add HazenSun/dsh-codex-bridge --skill setup-dsh-bridgegit 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/skills/hazensun/dsh-codex-bridge/setup-dsh-bridge)<a href="https://agentmods.dev/skills/hazensun/dsh-codex-bridge/setup-dsh-bridge"><img src="https://agentmods.dev/badge/skills/hazensun/dsh-codex-bridge/setup-dsh-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/skills/hazensun/dsh-codex-bridge/setup-dsh-bridge"><img src="https://agentmods.dev/badge/skills/hazensun/dsh-codex-bridge/setup-dsh-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00070 | $0.01739 |
| Opus 5.5 | $0.00028 | $0.00696 |
| Sonnet 5.5 | $0.00014 | $0.00348 |
| Haiku 4.5 | $0.00007 | $0.00174 |
Grade A, and why
setup-dsh-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 17d 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up DSH Bridge
Treat setup and model routing as a controlled configuration workflow. DSH owns Provider adapters and credentials; Bridge owns named execution Profiles, project defaults, safety limits, and routing. Never request, display, copy, or write an API key, Cookie, OAuth token, private endpoint, or credential value.
Installation contract
The Plugin provides Setup and Delegate Skills. Its installation alone does not register MCP. Bridge setup/install separately runs the official codex mcp add dsh-codex-bridge with an absolute Node executable, an absolute source-checkout launcher, and --env DSH_BRIDGE_RUNTIME_CONFIG=<absolute-runtime.json>.
Use the same Codex Home as the user's active CLI/Desktop. With a custom CODEX_HOME, run installation, codex mcp get dsh-codex-bridge --json, and any removal against that Home. Preserve the source checkout and dedicated DSH directory because the registered launcher references them. Do not reconstruct plugin .mcp.json, mcpServers, ${PLUGIN_ROOT} / ${CODEX_HOME} substitutions, or env_vars / envVars: the tested Codex 0.156.1 legacy plugin surface did not resolve them reliably.
Runtime selection is saved in that Home's dsh-codex-bridge/runtime.json. CLI environment overrides can select a different DSH executable/Home temporarily; to change Desktop, rerun setup and save the desired selection, then start a new task. The saved runtime is shared by Bridge projects under that Codex Home. Disabling the Skill plugin does not delete MCP registration. Remove it with codex mcp remove dsh-codex-bridge only when the user requested full removal and all affected Bridge projects have stopped using it.
Start with status
- Call
get_setup_statuswhen the Bridge MCP tools are available, before proposing a configuration change. - Follow only the returned
next_actions; do not guess that the installation is ready. - If MCP cannot start or registration is missing, inspect
codex mcp get dsh-codex-bridge --jsonand the Bridge launcher'sruntime.jsonunder$CODEX_HOME/dsh-codex-bridge/(default~/.codex/dsh-codex-bridge/). It holds non-secretcommand,dsh_home, andsource_rootpaths. Resolve the source checkout from this file or the user's installation request, and resolve the target Git top-level project. Preview<absolute-node> <source_root>/packages/cli/dist/index.js setup --project <git-root> --source <source_root> --dsh-bin <absolute-dsh> --dry-run. Execute the reviewed installation within existing authorization and the user's preview/confirmation preferences. The installer saves the runtime and registers MCP; use its compatible version, not another project's global DSH. If a same-name registration is not Bridge-managed, inspect the conflict and do not delete that service to bypass the guard. - Before first use of an older DSH Home, back up the affected settings or use an explicitly selected independent Home. DSH 0.2 can migrate legacy
settings.yaml; a separate executable alone does not isolate its data. Recheck registration anddoctorafter installation, then start a new task to discover the setup tools. - Stop at a clear manual action when DSH needs a credential. Tell the user to configure it in the
codex-bridgeDSH Profile or through an approved environment-variable reference, then rerun status. Never accept the literal secret in chat.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 17d ago Changed · +14 lines 9d8140a5be4c
- 1mo ago First seen · 46 lines · 70 tokens per session scan A aa1ea32e35fa
setup-dsh-bridge is a skill published in the GitHub repository HazenSun/dsh-codex-bridge (1 stars, last pushed 17d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,739 once invoked, about $0.0003 per session on Opus 5.5. 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 skills, from other repositories
shortfilm-prompt
A five-part method for writing prompts for AI-generated videos, such as Sora or Seedance. It organizes each prompt into the subject, setting, visual style, camera movement, and timed shots with sound.
ao-workflow-runner
A workflow engine that reads YAML files and runs tasks assigned to different named roles. YAML is a text format for describing structured settings and steps.
skill
Ten native DSH tools give a text-only agent eyes. Use these structured tools directly; do not shell out to the bundled Python scripts or reproduce their implementation. Vision API credentials and model settings are managed by the plugin, so tool calls do not receive credentials.
eac-desktop-tips
A quick reference for using and troubleshooting features in the Deepseek Harness EAC desktop client. It covers window behavior, conversation rollback, plugins, desktop pets, Skills, MCP services, updates, and logs.
submit-dsh-plugin
A submission checklist and workflow for adding a DeepSeek Harness plugin to the community’s public catalogue. It prepares the catalogue entry and checks the plugin’s repository, metadata, tests, and required files.
dsh-plugin-guide
Use when developing, reviewing, packaging, debugging, or answering questions about DeepSeek Harness (DSH) plugins — the plugin-based agent harness on vendored Cordis. Applies the official plugin-development constraints (plugin contract, cordis.yml layers, services/events/effects, tool DSL, bundles/profiles) backed by…