Preface¶

The DeepSeek Harness (DSH) plugin ecosystem emphasizes modularity and extensibility. Everything Claude Code (ECC) provides a mature agent definition and skills system, but it cannot be directly embedded in the DSH runtime natively. The staavanothanh/dsh-ecc plugin acts as an adaptation layer, converting ECC agent Markdown resources into DSH-recognizable personas and instructions, and exposing ECC skills through the DSH skill provider. It is not a fork of DSH, but a runtime adapter package aimed at solving how to reuse ECC capabilities within DSH workflows.

Core Capabilities¶

This plugin integrates ECC resources into the DSH environment in the following ways:

1. Resource mapping: Converts ECC agent Markdown into persona and instruction resources for child agents.
2. Skill provisioning: Discovers, validates, and loads ECC skills through the DSH skill provider.
3. Lifecycle injection: Uses DSH lifecycle hooks to inject model, provider, and reasoning effort catalogs into the runtime environment.
4. Native tool implementations: Implements the DSH native tools spawn and spawn_fork, supporting explicit provider/model selection and conditional reasoning effort.
5. Session seeding: spawn_fork uses DSH’s fork provider to inject completed rounds from the parent session as seeds into a child session, enabling context inheritance.

Installation¶

Install the officially released tarball package into the specified DSH profile:

dsh plugin --profile web add https://github.com/staavanothanh/dsh-ecc/releases/download/v0.7.0/staavanothanh-dsh-ecc-0.7.0.tgz

After installation, the plugin is extracted into the DSH profile directory, including resources such as assets/ecc/agents and assets/ecc/skills.

Usage Examples¶

Spawn a Child Agent¶

Use the spawn tool to start a child agent, specifying the provider, model, reasoning effort, and ECC persona.

{
  "operation": "start",
  "prompt": "Review the authentication boundary and report concrete risks.",
  "provider": "deepseek-official",
  "model": "deepseek-v4-flash",
  "effort": "high",
  "persona": "ecc:security-reviewer",
  "label": "security-review"
}

Continue the Conversation¶

Use the followup operation to continue a previously started child agent.

{
  "operation": "followup",
  "childId": "<durable-child-id>",
  "prompt": "Now verify the highest-risk finding against the current tests."
}

Fork Mode¶

spawn_fork uses the same interface contract as spawn, but starts the child session through DSH’s fork provider. The child session receives the context of completed rounds from the parent session, while the current round is excluded.

{
  "operation": "start",
  "prompt": "Analyze the context inherited from the parent session.",
  "provider": "deepseek-official",
  "model": "deepseek-v4-flash",
  "effort": "medium",
  "persona": "ecc:code-reviewer"
}

Notes¶

1. Namespace mapping: DSH’s native skill registry only accepts kebab-case names. ECC internal identifiers (such as ecc:accessibility) are mapped to accessibility. Therefore, /ecc:name and /name may point to different resources; currently /name is the effective entry point.
2. MCP configuration: The plugin does not include MCP servers; MCP servers must be configured separately in DSH.
3. Skill conflicts: If the project contains a skill with the same name, it may override the ECC candidate resource; pay attention to scope and priority.
4. Fork provider dependency: The host must provide the fork provider; otherwise, calling spawn_fork will return TRANSPORT_UNAVAILABLE.
5. Reasoning effort field: Not all models expose reasoning effort metadata. If the selected model lacks effort metadata, the plugin omits the reasoningEffort field, and the default value from DSH or the provider will apply.

Conclusion¶

As a lightweight adapter, dsh-ecc bridges the gap between the ECC ecosystem and the DSH ecosystem, allowing developers to directly use ECC agent definitions and skills within DSH workflows. Through native tool interfaces and the fork mechanism, it provides flexible child-agent management capabilities.

GitHub repository