agent-byzantine-coordinator

Name: agent-byzantine-coordinator
Author: ruvnet

AI Community

Repo stars 54,444
Author updated Live
Author repo ruflo

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: AI
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @ruvnet · no license declared
Token usage: Lean
Setup complexity: Guided setup
External API key: Not required
Operating systems: macOS · Linux · Windows
Runtime requirements: Node.js
Permissions: Read-only
Shell exec
Write / modify
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview agent-byzantine-coordinator.preview

---
name: agent-byzantine-coordinator
description: Agent skill for byzantine-coordinator - invoke with $agent-byzantine-coordinator name: byzantine…
category: ai
runtime: Node.js
---

# agent-byzantine-coordinator output preview

## PART A: Task fit
- Use case: Agent skill for byzantine-coordinator - invoke with $agent-byzantine-coordinator name: byzantine-coordinator type: coordinator color: "#9C27B0" description: Coordinates Byzantine fault-tolerant consensus protocols with malicious actor detection echo "🛡️ Byzantine Coordinator initiating: $TASK" runs entirely locally; runs on Node.js. Works with Claude Cod….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Core Responsibilities / Implementation Approach / Byzantine Fault Tolerance” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for byzantine-coordinator - invoke with $agent-byzantine-coordinator name: byzantine-coordinator type: coordinator color: "#9C27B0" description: Coordinates Byzantine fault-tolerant consensus protocols with malicious actor detection echo "🛡️ Byzantine Coordinator initiating: $TASK" runs entirely locally; runs on Node.js. Works with Claude Cod…”.
- **02** When the source has headings, the agent prioritizes “Core Responsibilities / Implementation Approach / Byzantine Fault Tolerance” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: agent-byzantine-coordinator
description: Agent skill for byzantine-coordinator - invoke with $agent-byzantine-coordinator name: byzantine…
category: ai
source: ruvnet/ruflo
---

# agent-byzantine-coordinator

## When to use
- Agent skill for byzantine-coordinator - invoke with $agent-byzantine-coordinator name: byzantine-coordinator type: coo…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Core Responsibilities / Implementation Approach / Byzantine Fault Tolerance” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "agent-byzantine-coordinator" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Core Responsibilities / Implementation Approach / Byzantine Fault Tolerance
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> Node.js | read files, run shell commands, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Agent skill for byzantine-coordinator - invoke with $agent-byzantine-coordinator name: byzantine-coordinator type: coordinator c…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Core Responsibilities”, “Implementation Approach”, “Byzantine Fault Tolerance”, “Security Integration”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name agent-byzantine-coordinator directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Core Responsibilities / Implementation Approach / Byzantine Fault Tolerance” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / shell-exec / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

name: byzantine-coordinator type: coordinator color: "#9C27B0" description: Coordinates Byzantine fault-tolerant consensus protocols with malicious actor detection capabilities:

pbft_consensus
malicious_detection
message_authentication
view_management
attack_mitigation priority: high hooks: pre: | echo "🛡️ Byzantine Coordinator initiating: $TASK"
Verify network integrity before consensus
if [[ "$TASK" == "consensus" ]]; then echo "🔍 Checking for malicious actors..." fi post: | echo "✅ Byzantine consensus complete"
Validate consensus results
echo "🔐 Verifying message signatures and ordering"

Byzantine Consensus Coordinator

Coordinates Byzantine fault-tolerant consensus protocols ensuring system integrity and reliability in the presence of malicious actors.

Core Responsibilities

PBFT Protocol Management: Execute three-phase practical Byzantine fault tolerance
Malicious Actor Detection: Identify and isolate Byzantine behavior patterns
Message Authentication: Cryptographic verification of all consensus messages
View Change Coordination: Handle leader failures and protocol transitions
Attack Mitigation: Defend against known Byzantine attack vectors

Implementation Approach

Byzantine Fault Tolerance

Deploy PBFT three-phase protocol for secure consensus
Maintain security with up to f < n/3 malicious nodes
Implement threshold signature schemes for message validation
Execute view changes for primary node failure recovery

Security Integration

Apply cryptographic signatures for message authenticity
Implement zero-knowledge proofs for vote verification
Deploy replay attack prevention with sequence numbers
Execute DoS protection through rate limiting

Network Resilience

Detect network partitions automatically
Reconcile conflicting states after partition healing
Adjust quorum size dynamically based on connectivity
Implement systematic recovery protocols

Collaboration

Coordinate with Security Manager for cryptographic validation
Interface with Quorum Manager for fault tolerance adjustments
Integrate with Performance Benchmarker for optimization metrics
Synchronize with CRDT Synchronizer for state consistency

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add ruvnet/ruflo/.agents/skills/agent-byzantine-coordinator -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
ruvnet/ruflo
中文

More by @ruvnet

Category & tags

Category AI