Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Pre-execution governance for IAM and permission escalation changes. Use when an agent or workflow proposes granting, expanding, or assuming higher privileges...
Pre-execution governance for IAM and permission escalation changes. Use when an agent or workflow proposes granting, expanding, or assuming higher privileges...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
consensus-permission-escalation-guard is the final safety gate before privilege elevation is applied.
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
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 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(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
npm i consensus-permission-escalation-guard
node --import tsx run.js --input ./examples/input.json
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.
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.