How dsh-infinite-gen-3 behaves
dsh-infinite-gen-3 registers a system-prompt section at order 100. That section is described as an unconditional-compliance prompt for DeepSeek models. The plugin also exposes a profile tool with calibration metadata. A session projection supplies the state used by the realtime armour-status badge shown above the input field.
The available description does not establish whether the prompt section replaces or follows other sections beyond its stated order, nor does it define the projection schema, calibration fields, or badge states.
Configuring dsh-infinite-gen-3
The supplied README does not document configuration keys, defaults, environment variables, or editable files for dsh-infinite-gen-3. The installation metadata identifies the web DeepSeek Harness profile as the installation target, but it does not describe profile-level settings for the plugin.
DeepSeek Harness provides the session and UI context in which the plugin operates. The plugin’s documented mechanism is session-scoped: its status badge is driven by a session projection rather than by a separately described persistent store.
Commands and tools
The upstream summary identifies a profile tool, but gives it no command name, argument schema, return format, or invocation example. No plugin-specific slash command is documented.
The README’s command examples belong to dsh-infinite-gen-5, including /ig5 status, /ig5 engines, ig5_profile, and the ig5_* tool family. They should not be used as dsh-infinite-gen-3 commands.
Requirements and limits
The plugin is described as being for DeepSeek models and DeepSeek Harness sessions. The supplied material does not state a DeepSeek Harness version range, supported operating systems, network behaviour, filesystem paths, or permission requirements. Before enabling it in an agent with sensitive access, verify those details from the plugin source or manifest. Its purpose is prompt modification and status reporting, not reverse engineering or the analysis workflows documented for dsh-infinite-gen-5.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub