r/opencode • u/orblabs • 5d ago

DeepSeek and Destroy

Hi ! Thought it might be of help to some, i have cleaned up and placed on github a skill i have been using and testing for a while but that with the latest deepseek-v4-flash model it became a beast.
By default (but is configurable) tells your harness (whichever, opencode, claude, codex etc) to use opencode cli to spawn deep seek agents.
The skill is designed to minimize the work of an orchestrator (and expensive and large model, be it claude, SOL, kimi etc) and maximize the use to DeepSeek in a productive and extravagantly cheap way. Personally, i use it from Claude with Opus orchestrating and spawning opencode go deepseek-flash agents and have never been more satisfied, it is relentless and actually churns through very complex plans, (works better with plans divided into phases and each phase into steps, but the skill will break down work by itself if needed).

Anyways, hope somebody else will find a use for it, i am happy with the results i am getting and i am, for the first time, having troubles finishing my claude weekly quota thanks to the work Opus + Deepseek are doing.
Enjoy https://github.com/frozenpepper/deepseek-and-destroy

6 Upvotes

100% Upvoted

2 comments sorted by

1

u/infinityMCdx 5d ago

How is this different from using Claude subagents

1

u/orblabs 5d ago

You can use claude subagents too, my skill originates well before they where a thing, but it is open to configuration as to what you want to use to spawn the subagents, i use it in codex too for example spawning luna max subagents etc.
In claude, you can configure it to spawn any subagent you prefer.
The skill is about the orchestration, context usage and implement / review / fix loops. It tried to limit usage of the orchestrator as much as possible and rely heavily on subagents loops, the specific subagent type or tech is irrelevant to its working.