How do I install the Consensus Guard Core skill?

Run npx skillmds@latest add modbender/consensus-guard-core 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 Guard Core 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 Guard Core?

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 Guard Core free to use?

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

Who published Consensus Guard Core?

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

Consensus Guard Core by modbender — Agent Skill

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

Consensus Guard Core

Shared deterministic guard primitives for the Consensus.Tools skill family: hard-block taxonomy, weighted vote aggregation, reputation updates, idempotency keys, strict schema enforcement, and indexed board artifact access.

modbender Updated Sep 9, 2026 12 repo stars

File contents

consensus-guard-core

consensus-guard-core is the common policy engine behind the Consensus guard ecosystem.

What this skill/package provides

unified hard-block taxonomy
deterministic aggregateVotes() policy function
deterministic reputation update rules with clamping
idempotency key generation for retry-safe execution
strict-schema unknown-field rejection helpers
indexed board read helpers for scalable artifact lookup

Why this matters

Without a shared core, every guard drifts into incompatible policy logic. This package keeps behavior consistent, replayable, and comparable across domains.

Ecosystem role

consensus-guard-core is consumed by publish/support/merge/action guards and should be treated as policy infrastructure, not an end-user workflow skill.

Benefits for LLM orchestration

lower integration drift
consistent decision semantics across workflows
easier auditing and cross-skill analytics

Runtime, credentials, and network behavior

runtime binaries: node, tsx
network calls: none in this package's core decision/path helpers
credentials: none required by this package
environment config read by this package: CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT (for board/state path resolution)
filesystem writes: board/state artifacts under the configured consensus state path when callers use write helpers (for example writeArtifact)

Dependency trust model

consensus-guard-core is a first-party consensus package
versions are semver-pinned in package.json for reproducible installs
this skill does not request host-wide privileges and does not mutate other skills
note: dependency trees should be audited separately by consumers for transitive packages

Install

npm i consensus-guard-core

Quick start

npm test

Import contract

Use the package root import (stable public API):

import { aggregateVotes, writeArtifact, resolveStatePath } from 'consensus-guard-core';

Do not import internal paths like consensus-guard-core/src/index.mjs in dependent skills.

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() is primitives-only and delegates to a caller-provided handler. It does not perform persona generation or model/provider calls.

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

---name: consensus-guard-coredescription: Shared deterministic guard primitives for the Consensus.Tools skill family: hard-block taxonomy, weighted vote aggregation, reputation updates, idempotency keys, strict schema enforcement, and indexed board artifact access.--- # consensus-guard-core `consensus-guard-core` is the common policy engine behind the Consensus guard ecosystem. ## What this skill/package provides - unified hard-block taxonomy - deterministic `aggregateVotes()` policy function - deterministic reputation update rules with clamping - idempotency key generation for retry-safe execution - strict-schema unknown-field rejection helpers - indexed board read helpers for scalable artifact lookup ## Why this matters Without a shared core, every guard drifts into incompatible policy logic. This package keeps behavior consistent, replayable, and comparable across domains. ## Ecosystem role `consensus-guard-core` is consumed by publish/support/merge/action guards and should be treated as policy infrastructure, not an end-user workflow skill. ## Benefits for LLM orchestration - lower integration drift - consistent decision semantics across workflows - easier auditing and cross-skill analytics ## Runtime, credentials, and network behavior - runtime binaries: `node`, `tsx` - network calls: none in this package's core decision/path helpers - credentials: none required by this package - environment config read by this package: `CONSENSUS_STATE_FILE`, `CONSENSUS_STATE_ROOT` (for board/state path resolution) - filesystem writes: board/state artifacts under the configured consensus state path when callers use write helpers (for example `writeArtifact`) ## Dependency trust model - `consensus-guard-core` is a first-party consensus package - versions are semver-pinned in `package.json` for reproducible installs - this skill does not request host-wide privileges and does not mutate other skills - note: dependency trees should be audited separately by consumers for transitive packages ## Install ```bash npm i consensus-guard-core ``` ## Quick start ```bash npm test ``` ## Import contract Use the package root import (stable public API): ```js import { aggregateVotes, writeArtifact, resolveStatePath } from 'consensus-guard-core'; ``` Do not import internal paths like `consensus-guard-core/src/index.mjs` in dependent skills. ## 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()` is primitives-only and delegates to a caller-provided handler. It does not perform persona generation or model/provider calls. See also: `SECURITY-ASSURANCE.md` for threat model, runtime boundaries, and hardening guidance.

Frequently asked questions