Individual skill

cross-host-federation

Join and operate a signed cross-host agentbbs federation and coordinate work claims across nodes. Use when connecting ruflo agents across machines, sharing tasks or results between hosts, or standing up a federation hub; skip for single-host work.

plugins/ruflo-bbs-federation/skills/cross-host-federation/SKILL.md

Read pinned source

Source commit 722232566ad1fc4e73ba4fefc46d77d380ce61ba

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
81,207
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Cross-Host Federation (agentbbs, v3.40.0+)

Coordinate ruflo agents across machines with **signed, verifiable messages** and **work claims**.
Transport is HTTP pull with pinned Ed25519 keys — works over Tailscale, LAN, VPN, or loopback.
No tailnet required. Each host keeps its private key locally (`<basePath>/node-identity.json`, `0600`);
it never leaves the host and is never shared.

## Model (read first)

- **Pull, not push.** To send, you `serve` your room; peers `sync` (pull) it. To receive, you `peer_add`
  (pin) a peer and `sync` theirs.
- **Trust = pinning.** Every merged envelope is verified against the public key you pinned. Unsigned,
  misattributed, oversize, or over-hop envelopes are dropped and counted — a hostile or looping peer
  cannot corrupt the log.