cli-forge-quorum

A command-line generator for coordinating several software agents with voting, failure handling, and signed decision records. Byzantine fault tolerance means the group can continue making decisions even when some participants behave incorrectly.

In plain words
What is it for?
Use it for multi-agent coding work, compliance reviews, incident response, or tasks where workers have different levels of importance.
Why use it?
It reduces dependence on one coordinating agent and provides a way to handle stalled or faulty workers.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/destynova2/cli-code-skills/cli-forge-quorum
Any agent
npx skills add Destynova2/cli-code-skills --skill cli-forge-quorum
Clone the repo
git clone --depth 1 https://github.com/Destynova2/cli-code-skills

Made for: Claude Code, Codex.

Per session 159 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,185 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00159 $0.04185
Opus 5 $0.00079 $0.02093
Sonnet 5 $0.00032 $0.00837
Haiku 4.5 $0.00016 $0.00419

Measured 2d ago against content hash 7aeef4983a8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

cli-forge-quorum scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

11. **`{project}/.claude/settings.local.json`** — root permissions (see Reused artefacts below)
cli-forge-quorum/SKILL.md · 231 lines

How it starts

The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cli-forge-quorum — REC-Quorum Orchestration (BFT-grade)

Generates a multi-agent orchestration with Byzantine fault tolerance, adaptive quorum sizing per task criticality, and view-change timeouts to eliminate single-leader bottlenecks.

The pattern comes from applying distributed-systems research (PBFT, HotStuff, Mir-BFT, Mercury, BFTBrain) to LLM agent dispatch. Empirically validated by arxiv 2511.15755 — multi-agent orchestration raises actionable-recommendation rate from 1.7% to 100% with zero variance across 348 trials.

When to use this skill (triage)

Situation Use
First multi-agent sprint, 2-5 workers, dev repo cli-forge-chef (Brigade pattern, lighter)
Brigade stalled 30+ min on leader bottleneck cli-forge-quorum (view-change, leaderless)
Compliance audit / SLA / incident response cli-forge-quorum (signed trail + DQ metric)
> 10 parallel agents cli-forge-quorum (Mir-BFT-style scaling)
Variable criticality (trivial-to-critical tasks mixed) cli-forge-quorum (adaptive N)
"Just automate my git workflow" cli-forge-chef

Key test : if stalling the leader would cost > 1h of wasted sprint time, you need REC-Quorum. If the leader can stall and be manually unblocked in < 15 min, Brigade is enough.

Architecture — three phases, each gated

Phase 0 — Reflect    → plan signé + tickets commis (Chef + 2 Sous-Chefs plan)
Phase 1 — Execute    → leaderless, tickets pré-signés, contre-chef-inter auto-approve
Phase 2 — Control    → f+1 validateurs indépendants signent le résultat

Each phase emits a signed certificate (hash canonique + signatures). Without the certificate, no transition to the next phase. A failing phase triggers view-change (backup takes over) or escalation (human in the loop).

Phase details

Read references/rec-phases.md for the complete specification of each phase, including timeouts, hash-canonical voting, and view-change protocol.

Read the full file on GitHub · 231 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 231 lines · 159 tokens per session scan B 7aeef4983a8c

Subscribe to this mod's changes

cli-forge-quorum is a skill published in the GitHub repository Destynova2/cli-code-skills (5 stars, last pushed 10d ago), licensed MIT. It adds 159 tokens to every session and 4,185 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.