agentic-qe: Skill for Claude Code

.agents/skills/ruflo/.agents/skills/agent-byzantine-coordinator/SKILL.md

agent-byzantine-coordinator is a skill for Claude Code from proffesor-for-testing/agentic-qe. It costs 25 tokens per session (478 once invoked), scanned A, a copy of agent-byzantine-coordinator, MIT.

A coordinator for Byzantine fault-tolerant consensus, a way for distributed computers to agree even when some participants act maliciously or send false messages.

In plain words
What is it for?
Use it to manage PBFT consensus rounds, authenticate messages, detect malicious behavior, handle leader changes, and mitigate attacks.
Why use it?
It helps maintain a trustworthy shared decision when network participants may fail, lie, or become unavailable.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

This is proffesor-for-testing/agentic-qe's own configuration. It tells Claude Code how to work on agentic-qe itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentic-qe configures →

Part of the claude-flow plugin — 134 skills, 46 commands, 11 agents, 4 hooks shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to proffesor-for-testing/agentic-qe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/proffesor-for-testing/agentic-qe/main/.agents/skills/ruflo/.agents/skills/agent-byzantine-coordinator/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 134 skills, 46 commands, 11 agents, 4 hooks.

Wrote 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.

agentmods badge for agent-byzantine-coordinator

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-byzantine-coordinator.svg)](https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-byzantine-coordinator)
Your own site
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-byzantine-coordinator"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-byzantine-coordinator.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 478 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00025 $0.00478
Opus 5 $0.00013 $0.00239
Sonnet 5 $0.00005 $0.00096
Haiku 4.5 $0.00003 $0.00048

Measured 8d ago against content hash f047644e4725, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 8d 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.

Origin

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.

.agents/skills/ruflo/.agents/skills/agent-byzantine-coordinator/SKILL.md · 68 lines

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

  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

Read the full file on GitHub · 68 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. 8d ago First seen · 68 lines · 25 tokens per session scan A f047644e4725

Subscribe to this mod's changes

agent-byzantine-coordinator is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (475 stars, last pushed yesterday), 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.

Related

Other skills, from other repositories

foundry-config-setup

Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.

microsoft/agent-framework · 65 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

tooluniverse-drug-research

Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…

mims-harvard/ToolUniverse · 71 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens

gh-bulk-issues

Orchestrate parallel Mastra Code headless instances to debug and fix multiple GitHub issues simultaneously.

mastra-ai/mastra · 25 tokens

qa-investigation

Investigate a specific test failure to its root cause and document the why. Detects whether a failing test is flaky (intermittent) or a deterministic bug during reproduction. Use when a test fails and you need the real cause, not just to make it green. Execution layer, not strategy review. Keywords: flaky test…

fugazi/test-automation-skills-agents · 94 tokens