AI Agent Hub
Back to plugins
🧩

dsh-policy-strict-gate

admin-security Updated 2026.09.11

Run the following command in DeepSeek Harness:

dsh plugin install catsenior507/dsh-policy-strict-gate

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install catsenior507/dsh-policy-strict-gate inside your DeepSeek Harness profile to install this plugin, sourced from https://github.com/catsenior507/dsh-policy-strict-gate , then restart the host to activate the gates.

About this plugin

The moment a model needs a check most is the moment it is least likely to run one voluntarily: when it is confident, rushing, or already looping. dsh-policy-strict-gate elevates strict_check and the failure journal from tools the agent may call into policy the harness enforces, so a refusal lands before the next write rather than after the fact.

Three independently configured gates do the heavy lifting. The repeated-failure gate detects the same failure signature recurring in a session and injects a targeted remediation notice, deliberately keyed to tools/result so even pipeline-level denials count toward the threshold. The critical-path gate refuses writes to glob-protected paths until a covering Lean specification is accepted, while keeping the repair path open so the fix to the very error it reported is never blocked. The post-write syntax gate runs the language native checker immediately after every accepted write, catching a broken edit at the step that broke it instead of three commands later through an unrelated failure.

Built for DeepSeek Harness users who want security validation without relying on model self-discipline. No build step, no runtime dependencies; the strict-check package is optional at load time, and the repeated-failure gate remains active even without it, so policy can be tightened incrementally.

Use Cases

  • Break agents out of repeated-failure retry loops
  • Enforce Lean spec acceptance before writes to critical paths
  • Run language-native syntax checks immediately after every accepted write

Best For

  • DeepSeek Harness developers who want security checks enforced by the harness, not the model
  • Small teams that need independent safety gates to govern agent write behavior
  • Security engineers who prefer policy-driven controls over prompt-based constraints