How do I install the Consensus Support Reply Guard skill?

Run npx skillmds@latest add modbender/consensus-support-reply-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 Support Reply 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 Support Reply 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 Support Reply Guard free to use?

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

Who published Consensus Support Reply Guard?

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

Consensus Support Reply Guard by modbender

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

Consensus Support Reply Guard

Risk-aware support response governance with persona-weighted consensus. Detects legal/sensitive/confidentiality issues, applies hard-block policy checks, and writes auditable decision artifacts for customer-facing automation.

modbender Updated Sep 9, 2026 12 repo stars

File contents

consensus-support-reply-guard

consensus-support-reply-guard is a customer-trust guard for support workflows.

What this skill does

evaluates support drafts before sending
detects high-risk claim patterns
blocks or rewrites responses when policy violations appear
updates persona reputations based on final decision alignment
preserves decision history in board artifacts

Why this matters

Support replies are high-frequency and brand-critical. This skill prevents overconfident legal/PII mistakes at scale.

Ecosystem role

Composes with consensus board state using explicit vote inputs and deterministic guard decisions.

Ideal scenarios

automated ticket triage replies
L1/L2 AI response review gates
regulated or enterprise support channels

Runtime, credentials, and network behavior

runtime binaries: node, tsx
network calls: none in the guard decision path itself
filesystem writes: board/state artifacts under the configured consensus state path

Dependency trust model

consensus-guard-core is the first-party consensus package used in guard execution
versions are semver-pinned in package.json for reproducible installs
this skill does not request host-wide privileges and does not mutate other skills

Quick start

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

Tool-call integration

This skill is wired to the consensus-interact contract boundary (via shared consensus-guard-core wrappers where applicable):

readBoardPolicy
getLatestPersonaSet / getPersonaSet
writeArtifact / writeDecision
idempotent decision lookup

This keeps board orchestration standardized across skills.

Invoke Contract

This skill exposes a canonical entrypoint:

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

invoke() starts the guard flow and executes deterministic policy evaluation with board operations via shared guard-core wrappers.

external_agent mode

Guards support two modes:

mode="external_agent": caller supplies external_votes[] from agents/humans/models for deterministic aggregation.
mode="persona": requires an existing persona_set_id; guard will not generate persona sets internally.

---name: consensus-support-reply-guarddescription: Risk-aware support response governance with persona-weighted consensus. Detects legal/sensitive/confidentiality issues, applies hard-block policy checks, and writes auditable decision artifacts for customer-facing automation.--- # consensus-support-reply-guard `consensus-support-reply-guard` is a customer-trust guard for support workflows. ## What this skill does - evaluates support drafts before sending - detects high-risk claim patterns - blocks or rewrites responses when policy violations appear - updates persona reputations based on final decision alignment - preserves decision history in board artifacts ## Why this matters Support replies are high-frequency and brand-critical. This skill prevents overconfident legal/PII mistakes at scale. ## Ecosystem role Composes with consensus board state using explicit vote inputs and deterministic guard decisions. ## Ideal scenarios - automated ticket triage replies - L1/L2 AI response review gates - regulated or enterprise support channels ## Runtime, credentials, and network behavior - runtime binaries: `node`, `tsx` - network calls: none in the guard decision path itself - filesystem writes: board/state artifacts under the configured consensus state path ## Dependency trust model - `consensus-guard-core` is the first-party consensus package used in guard execution - versions are semver-pinned in `package.json` for reproducible installs - this skill does not request host-wide privileges and does not mutate other skills ## Quick start ```bash node --import tsx run.js --input ./examples/input.json ``` ## Tool-call integration This skill is wired to the consensus-interact contract boundary (via shared consensus-guard-core wrappers where applicable): - readBoardPolicy - getLatestPersonaSet / getPersonaSet - writeArtifact / writeDecision - idempotent decision lookup This keeps board orchestration standardized across skills. ## Invoke Contract This skill exposes a canonical entrypoint: - `invoke(input, opts?) -> Promise<OutputJson | ErrorJson>` `invoke()` starts the guard flow and executes deterministic policy evaluation with board operations via shared guard-core wrappers. ## external_agent mode Guards support two modes: - `mode="external_agent"`: caller supplies `external_votes[]` from agents/humans/models for deterministic aggregation. - `mode="persona"`: requires an existing `persona_set_id`; guard will not generate persona sets internally.

Frequently asked questions