Model plugins for DeepSeek Harness
Add providers, route requests and keep an eye on usage.
Model plugins sit between the harness and the models it calls. Some add a provider, including locally hosted models, some decide which model handles which request, and some record token counts and cost. They are worth a look when you want a model the harness does not offer by default, or when the bill has started to matter.
2 plugins
- dsh-our-free-modelEbony-Vinyl Adds anonymous free model channels, account-based channels and provider integrations to DSH. Includes fallback chains, local usage statistics and an OpenAI- and Anthropic-compatible gateway. Models 71.3k
- dsh-routing-suiteyjh051108 One repository that bundles a runtime injector, the Router Standard and Router Spec presets, and a graded task protocol with check-ins and a red-team gate. Models 7k
How to choose
These plugins see your API keys and every prompt, so prefer ones with readable source and no unexplained network calls. For a provider plugin, check that it supports the features you rely on, such as streaming and tool calls, since not every model or endpoint handles them the same way. Usage figures from a plugin are estimates based on what it observed; the provider's own billing page is the number that counts.
Terms used on this page
- Provider
- A service or local runtime that hosts models and answers requests for them.
- Routing
- Rules that choose which model receives a request, for example by task type, cost or availability.
- Token usage
- The count of input and output tokens for a request, which is what most providers bill on.
Questions and answers
Can I use models other than DeepSeek's?
That is what provider plugins are for, and which models are covered depends on the plugin. How well another model performs is a separate matter, particularly with tool calls, so test it on your own tasks.
Why does the usage shown by a plugin differ from my provider's bill?
The plugin counts what passes through it and applies a price table that may be out of date. Cached tokens, retries and requests made outside the harness also cause gaps. Use the plugin for trends and the provider for exact amounts.