How do I install the Consensus Deployment Guard skill?

Run npx skillmds@latest add modbender/consensus-deployment-guard in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Consensus Deployment Guard safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Consensus Deployment Guard?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Consensus Deployment Guard free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Consensus Deployment Guard?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Consensus Deployment Guard by modbender

Name: Consensus Deployment Guard
Rating: 4.2 (5 reviews)
Author: modbender

Consensus Deployment Guard

Pre-deployment governance for release and infrastructure rollout requests. Use when an agent or workflow proposes shipping code/config/infrastructure changes to staging or production and you need deterministic ALLOW/BLOCK/REQUIRE_REWRITE decisions with strict schema validation, idempotency, and board-native audit artifacts.

modbender Updated Sep 9, 2026 12 repo stars

File contents

consensus-deployment-guard

consensus-deployment-guard is the final safety gate before deployment execution.

What this skill does

validates deployment requests against a strict JSON schema (reject unknown fields)
evaluates hard-block and rewrite policy flags for release risk patterns
runs deterministic persona-weighted voting (or aggregates external votes)
returns one of: ALLOW | BLOCK | REQUIRE_REWRITE
writes decision artifacts for replay/audit

Decision policy shape

Hard-block examples:

required tests not passing
CI status failed
rollback artifact missing when required
incompatible schema migration
error budget already breached

Rewrite examples:

production rollout not using canary when policy requires it
initial rollout percentage above policy limit
production deploy missing explicit human confirmation gate
CI still pending
schema compatibility unknown

Runtime and safety model

runtime binaries: node, tsx
network behavior: none in guard decision logic
environment config read by this package: CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT
filesystem writes: consensus board/state artifacts under configured state path

Invoke contract

invoke(input, opts?) -> Promise<OutputJson | ErrorJson>

Modes:

mode="persona" (default): use local deterministic persona defaults for internal voting
mode="external_agent": consume external_votes[], aggregate deterministically, and enforce policy

Install

npm i consensus-deployment-guard

Quick start

node --import tsx run.js --input ./examples/input.json

Tests

npm test

Coverage includes schema rejection, hard-block paths, rewrite paths, allow paths, idempotent retries, and external-agent aggregation behavior.

See also: SECURITY-ASSURANCE.md for threat model, runtime boundaries, and deployment hardening guidance.

---name: consensus-deployment-guarddescription: Pre-deployment governance for release and infrastructure rollout requests. Use when an agent or workflow proposes shipping code/config/infrastructure changes to staging or production and you need deterministic ALLOW/BLOCK/REQUIRE_REWRITE decisions with strict schema validation, idempotency, and board-native audit artifacts.--- # consensus-deployment-guard `consensus-deployment-guard` is the final safety gate before deployment execution. ## What this skill does - validates deployment requests against a strict JSON schema (reject unknown fields) - evaluates hard-block and rewrite policy flags for release risk patterns - runs deterministic persona-weighted voting (or aggregates external votes) - returns one of: `ALLOW | BLOCK | REQUIRE_REWRITE` - writes decision artifacts for replay/audit ## Decision policy shape Hard-block examples: - required tests not passing - CI status failed - rollback artifact missing when required - incompatible schema migration - error budget already breached Rewrite examples: - production rollout not using canary when policy requires it - initial rollout percentage above policy limit - production deploy missing explicit human confirmation gate - CI still pending - schema compatibility unknown ## Runtime and safety model - runtime binaries: `node`, `tsx` - network behavior: none in guard decision logic - environment config read by this package: `CONSENSUS_STATE_FILE`, `CONSENSUS_STATE_ROOT` - filesystem writes: consensus board/state artifacts under configured state path ## Invoke contract - `invoke(input, opts?) -> Promise<OutputJson | ErrorJson>` Modes: - `mode="persona"` (default): use local deterministic persona defaults for internal voting - `mode="external_agent"`: consume `external_votes[]`, aggregate deterministically, and enforce policy ## Install ```bash npm i consensus-deployment-guard ``` ## Quick start ```bash node --import tsx run.js --input ./examples/input.json ``` ## Tests ```bash npm test ``` Coverage includes schema rejection, hard-block paths, rewrite paths, allow paths, idempotent retries, and external-agent aggregation behavior. See also: `SECURITY-ASSURANCE.md` for threat model, runtime boundaries, and deployment hardening guidance.

Frequently asked questions