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.
npx skills add henryalouf/ruflow --skill agent-byzantine-coordinatorgit clone --depth 1 https://github.com/henryalouf/ruflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/henryalouf/ruflow/agent-byzantine-coordinator)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-byzantine-coordinator"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-byzantine-coordinator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-byzantine-coordinator"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-byzantine-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.00478 |
| Opus 5 | $0.00013 | $0.00239 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
agent-byzantine-coordinator scanned grade A with 0 findings 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 9d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to agent-byzantine-coordinator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
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.
- 9d ago First seen · 68 lines · 25 tokens per session scan A f047644e4725
agent-byzantine-coordinator is a skill published in the GitHub repository henryalouf/ruflow (126 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 478 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-byzantine-coordinator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…