DeepSeek Harness plugins with client injection signals
Compare approved plugin records with client injection signals, then inspect each fixed-source report to see which captured evidence triggered the signal.
What the signal describes
Client injection signals identify records whose captured manifest or static analysis references a client contribution, such as scripts or styles added to a rendered interface. This collection is built only from DSH Hunt's eligible public catalog. It does not execute plugin code or infer browser behavior beyond the captured evidence; the record count and analysis summary below are recalculated from the published catalog.
8 eligible plugin records currently match this signal.
Capability signals summarize captured static evidence. DSH Hunt does not execute third-party plugin code, and a signal does not establish runtime behavior, compatibility, or safety.
Evidence summary
Use this page when reviewing how a plugin may contribute to browser-rendered content. Follow each report to the exact source commit, then read the linked evidence before drawing conclusions about what the plugin does at runtime.
Eligible plugin records
8
Records with static analysis
8 of 8
Static analysis findings
45
Declared platforms
web: 8
Most recent source analysis
How records enter this page
A record must pass the public catalog quality checks and have a completed static analysis result.
The published capability evidence must include the client-injection signal; records are listed once even if the signal appears more than once.
The source link points to the fixed commit used for the report, not to a moving default branch.
In-GUI skin center for the dsh web GUI — the single skin package: skins are pure asset directories (built-in plus $DSH_HOME/skins) loaded and rendered only by the skin center; live try-on and one-click apply switch atomically in the page (no reload, no cordis.patch.yml rewrite, no restart)
Multi-pet companion plugin for the dsh web GUI: a registry-driven floating pet that reacts to model activity, with per-pet naming, petting/feeding interactions and an affinity score
AgentTeams for DeepSeek Harness: multi-agent team collaboration (captain, members, tasks with dependencies, messaging) driven by natural language, with a tree monitor in the web GUI
Does this signal prove that a plugin changes the page at runtime?
No. It records a client contribution declared or found in the captured static evidence. DSH Hunt does not run the plugin, so runtime behavior still needs a separate review.
Why can this page appear with only a few records?
The page is useful for reviewing the current evidence, but it stays out of search results and the sitemap until the eligible collection reaches the configured minimum size.