Skip to content
cccskills
FreePublished on GitHub

agent-byzantine-coordinator

Coordinate agreement across distributed participants when some may fail or act maliciously. It covers PBFT, a three-phase agreement protocol, along with message authentication, malicious participant detection, leader replacement, and recovery from network partitions.

OriginalShow the original description

Agent skill for byzantine-coordinator - invoke with $agent-byzantine-coordinator

ruvnet/ruflo
See how to install

Good for

  • Planning consensus with potentially malicious participants
  • Checking vote authenticity and message ordering
  • Coordinating leader replacement after failure
  • Reconciling conflicting states after network recovery

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

  1. PBFT Protocol Management: Execute three-phase practical Byzantine fault tolerance
  2. Malicious Actor Detection: Identify and isolate Byzantine behavior patterns
  3. Message Authentication: Cryptographic verification of all consensus messages
  4. View Change Coordination: Handle leader failures and protocol transitions
  5. 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add-model-descriptions

FreeSummary

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-create

FreeSummary

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-index

FreeSummary

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-reindex

FreeSummary

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-review

FreeSummary

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-verify

FreeSummary

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo77.1KUpdated Oct 19, 2026

See all skills by ruvnet

Report a problem with this skill