governance-gate

Enforce governance policies for autonomous agent executions with sandboxing and rollback.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill governance-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governance-gate
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/governance-gate
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill governance-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Governance Gate enforces safety, policy, and recovery controls across autonomous agent executions to prevent destructive, privacy-leaking, or non-compliant operations and to ensure actions are auditable and reversible.

Core Features & Use Cases

  • Five safety layers: input sanitization, policy gating, execution sandbox, output validation, and recovery/rollback.
  • Seven policy constraints: safety, privacy, data access, financial, compliance, fairness, and transparency checks that block, redact, warn, or escalate as needed.
  • Escalation tiers and capability gating: T0–T3 risk tiers with explicit escalation behavior and enforcement of MCP server tool bindings; side-effect logging and git-safe workflows support recovery.
  • Use Cases: validating CI/CD deploys, gating database migrations, preventing secret leakage during code edits, and escalating financial or trading operations for human approval.

Quick Start

Ask governance-gate to evaluate and enforce policies for a proposed agent plan that would push infrastructure changes to production and return a compliant, escalated execution plan.

Frequently Asked Questions about governance-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce governance policies for autonomous agent executions?

Enforce governance policies for autonomous agent executions by applying input sanitization, seven policy constraints, execution sandboxing, output validation, side-effect logging, and rollback mechanisms to block, warn, or escalate risky operations.

What is the best way to prevent destructive operations during agent workflows?

Prevent destructive operations during agent workflows by enforcing five safety layers: input sanitization, policy gating, execution sandbox, output validation, and recovery or rollback mechanisms across tool invocations.

How do I add human approval escalation tiers for risky infrastructure changes?

Add human approval escalation tiers for risky infrastructure changes by assigning T0–T3 risk tiers that explicitly block, warn, or escalate destructive, financial, or non-compliant operations for review.

Can I enforce MCP server tool bindings and side-effect logging for agent runs?

Enforce MCP server tool bindings and side-effect logging for agent runs by applying capability gating and governance constraints that validate tool invocations and track irreversible infrastructure changes.

Does governance-gate support rollback mechanisms for CI/CD deploys and database migrations?

Governance-gate supports rollback mechanisms for CI/CD deploys and database migrations by validating execution plans, applying git-safe workflows, and logging side effects to ensure actions are auditable and reversible.

What policy constraints are checked to prevent secret leakage during code edits?

Policy constraints checked to prevent secret leakage during code edits include safety, privacy, data access, financial, compliance, fairness, and transparency checks that block, redact, warn, or escalate as needed.