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 Soulcynics404/AgentForge --skill agent-byzantine-coordinatorgit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/agent-byzantine-coordinator)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-byzantine-coordinator"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/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/soulcynics404/agentforge/agent-byzantine-coordinator"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/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 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.
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.
- 8d ago First seen · 68 lines · 25 tokens per session scan A f047644e4725
agent-byzantine-coordinator is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 15d 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
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.
clip-hand-skill
Expert knowledge for AI video clipping — yt-dlp downloading, whisper transcription, SRT generation, and ffmpeg processing.
twitter-hand-skill
Expert knowledge for AI Twitter/X management — API v2 reference, content strategy, engagement playbook, safety, and performance tracking.
package-author
A packaging guide for turning scripts, skills, or an MCP service into a standard plugin package. MCP is a way for an AI assistant to connect to external tools.
slack-tools
Slack workspace management and automation specialist.
routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.