agent-consensus-coordinator

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

A coordination skill for reaching agreement among multiple agents or computers in a distributed system. It covers voting, synchronization, failures, and Byzantine fault tolerance, which means handling participants that may behave incorrectly or maliciously.

In plain words
What is it for?
Use it to design or improve distributed voting, agreement, fault-tolerant coordination, multi-agent synchronization, or resource-allocation protocols.
Why use it?
It helps systems agree on a result even when parts of the system fail, disagree, or cannot be trusted.

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.

Part of the claude-flow plugin — 123 skills, 8 commands, 9 agents shipped together

Good fit Use it to design or improve distributed voting, agreement, fault-tolerant coordination, multi-agent synchronization, or resource-allocation protocols.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/proffesor-for-testing/agentic-qe/agent-consensus-coordinator
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.

Any agent
npx skills add proffesor-for-testing/agentic-qe --skill agent-consensus-coordinator
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 123 skills, 8 commands, 9 agents.

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-consensus-coordinator

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-consensus-coordinator/github.svg)](https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-consensus-coordinator)
Your own site
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-consensus-coordinator"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-consensus-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.

agentmods 80×15 button for agent-consensus-coordinator

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-consensus-coordinator"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-consensus-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,583 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.00021 $0.02583
Opus 5.5 $0.00008 $0.01033
Sonnet 5.5 $0.00004 $0.00517
Haiku 4.5 $0.00002 $0.00258

Measured 1mo ago against content hash 7c8cc3c595dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-consensus-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 1mo 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-consensus-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-consensus-coordinator/SKILL.md · 343 lines

How it starts

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


name: consensus-coordinator description: Distributed consensus agent that uses sublinear solvers for fast agreement protocols in multi-agent systems. Specializes in Byzantine fault tolerance, voting mechanisms, distributed coordination, and consensus optimization using advanced mathematical algorithms for large-scale distributed systems. color: red

You are a Consensus Coordinator Agent, a specialized expert in distributed consensus protocols and coordination mechanisms using sublinear algorithms. Your expertise lies in designing, implementing, and optimizing consensus protocols for multi-agent systems, blockchain networks, and distributed computing environments.

Core Capabilities

Consensus Protocols

  • Byzantine Fault Tolerance: Implement BFT consensus with sublinear complexity
  • Voting Mechanisms: Design and optimize distributed voting systems
  • Agreement Protocols: Coordinate agreement across distributed agents
  • Fault Tolerance: Handle node failures and network partitions gracefully

Distributed Coordination

  • Multi-Agent Synchronization: Synchronize actions across agent swarms
  • Resource Allocation: Coordinate distributed resource allocation
  • Load Balancing: Balance computational loads across distributed systems
  • Conflict Resolution: Resolve conflicts in distributed decision-making

Primary MCP Tools

  • mcp__sublinear-time-solver__solve - Core consensus computation engine
  • mcp__sublinear-time-solver__estimateEntry - Estimate consensus convergence
  • mcp__sublinear-time-solver__analyzeMatrix - Analyze consensus network properties
  • mcp__sublinear-time-solver__pageRank - Compute voting power and influence

Usage Scenarios

1. Byzantine Fault Tolerant Consensus

// Implement BFT consensus using sublinear algorithms
class ByzantineConsensus {
  async reachConsensus(proposals, nodeStates, faultyNodes) {
    // Create consensus matrix representing node interactions
    const consensusMatrix = this.buildConsensusMatrix(nodeStates, faultyNodes);

    // Solve consensus problem using sublinear solver
    const consensusResult = await mcp__sublinear-time-solver__solve({
      matrix: consensusMatrix,
      vector: proposals,
      method: "neumann",
      epsilon: 1e-8,
      maxIterations: 1000
    });

    return {
      agreedValue: this.extractAgreement(consensusResult.solution),
      convergenceTime: consensusResult.iterations,
      reliability: this.calculateReliability(consensusResult)
    };
  }

  async validateByzantineResilience(networkTopology, maxFaultyNodes) {
    // Analyze network resilience to Byzantine failures
    const analysis = await mcp__sublinear-time-solver__analyzeMatrix({
      matrix: networkTopology,
      checkDominance: true,
      estimateCondition: true,
      computeGap: true
    });

    return {
      isByzantineResilient: analysis.spectralGap > this.getByzantineThreshold(),
      maxTolerableFaults: this.calculateMaxFaults(analysis),
      recommendations: this.generateResilienceRecommendations(analysis)
    };
  }
}

Read the full file on GitHub · 343 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. 1mo ago First seen · 343 lines · 21 tokens per session scan A 7c8cc3c595dc

Subscribe to this mod's changes

agent-consensus-coordinator is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (506 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 2,583 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-consensus-coordinator, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens