How do I install the Consensus Permission Escalation Guard skill?

Run npx skillmds@latest add modbender/consensus-permission-escalation-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 Permission Escalation 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 Permission Escalation 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 Permission Escalation Guard free to use?

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

Who published Consensus Permission Escalation Guard?

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

Consensus Permission Escalation Guard by modbender

Name: Consensus Permission Escalation Guard
Rating: 4.666666666666667 (3 reviews)
Author: modbender

Consensus Permission Escalation Guard

Pre-execution governance for IAM and permission escalation changes. Use when an agent or workflow proposes granting, expanding, or assuming higher privileges 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-permission-escalation-guard

consensus-permission-escalation-guard is the final safety gate before privilege elevation is applied.

What this skill does

validates escalation requests against a strict input schema (reject unknown fields)
evaluates hard-block and rewrite policy flags for IAM risk patterns
runs 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:

wildcard permissions (*, : *, broad owner/admin jumps)
missing ticket reference when required
break-glass escalation without incident reference
separation-of-duties conflicts (e.g., create + approve authority)

Rewrite examples:

weak or non-actionable justification
temporary duration exceeds policy limit
production escalation requires explicit human confirmation gate

Runtime and safety model

runtime binaries: node, tsx
network behavior: none in deterministic guard 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): uses local deterministic persona defaults for internal voting
mode="external_agent": consume external_votes[], then aggregate and enforce policy deterministically

Install

npm i consensus-permission-escalation-guard

Quick start

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

Tests

npm test

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

Note: this skill depends on consensus-guard-core for aggregation/state helpers; review that package alongside this one for full runtime auditability.

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

---name: consensus-permission-escalation-guarddescription: Pre-execution governance for IAM and permission escalation changes. Use when an agent or workflow proposes granting, expanding, or assuming higher privileges and you need deterministic ALLOW/BLOCK/REQUIRE_REWRITE decisions with strict schema validation, idempotency, and board-native audit artifacts.--- # consensus-permission-escalation-guard `consensus-permission-escalation-guard` is the final safety gate before privilege elevation is applied. ## What this skill does - validates escalation requests against a strict input schema (reject unknown fields) - evaluates hard-block and rewrite policy flags for IAM risk patterns - runs 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: - wildcard permissions (`*`, `: *`, broad owner/admin jumps) - missing ticket reference when required - break-glass escalation without incident reference - separation-of-duties conflicts (e.g., create + approve authority) Rewrite examples: - weak or non-actionable justification - temporary duration exceeds policy limit - production escalation requires explicit human confirmation gate ## Runtime and safety model - runtime binaries: `node`, `tsx` - network behavior: none in deterministic guard 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): uses local deterministic persona defaults for internal voting - `mode="external_agent"`: consume `external_votes[]`, then aggregate and enforce policy deterministically ## Install ```bash npm i consensus-permission-escalation-guard ``` ## Quick start ```bash node --import tsx run.js --input ./examples/input.json ``` ## Tests ```bash npm test ``` Test coverage includes schema rejection, hard-block paths, rewrite paths, allow paths, idempotent retries, and external-agent aggregation behavior. Note: this skill depends on `consensus-guard-core` for aggregation/state helpers; review that package alongside this one for full runtime auditability. See also: `SECURITY-ASSURANCE.md` for threat model, runtime boundaries, and deployment hardening guidance.

Frequently asked questions