How do I install the Pi Messenger Swarm Foundation skill?

Run npx skillmds@latest add ryan-brosas/pi-messenger-swarm-foundation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pi Messenger Swarm Foundation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pi Messenger Swarm Foundation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pi Messenger Swarm Foundation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pi Messenger Swarm Foundation?

ryan-brosas (@ryan-brosas) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pi Messenger Swarm Foundation by ryan-brosas

Name: Pi Messenger Swarm Foundation
Author: ryan-brosas

Pi Messenger Swarm Foundation

Use when building multi-agent coordination WITHOUT a central database or orchestrator process — durable agent registries with lockless name claiming, append-only event-sourced task queues with claim/dependency/cascade semantics, kafka-like feed messaging that tolerates offline recipients, subagent spawning with concurrency ceilings and crash-reconciled lifecycle tracking, or any port of the pi-messenger-swarm mesh to another agent host. Source code and direct tests are ground truth; references carry decisive excerpts and graph retrieval.

ryan-brosas Updated Sep 17, 2026

File contents

pi-messenger-swarm: file-based multi-agent swarm coordination foundation

Foundation contract

This is a cold, source-specific foundation, not an operational procedure. It is historical, revision-pinned evidence rather than timeless guidance. Current project source, tests, requirements, and runtime behavior outrank this projection and decide what ships.

Provenance and revision

Source record: pi-messenger-swarm; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.
Recorded revision: main@6fe429a4b74ae276a621bb72910d7926fb6b3104.
Full provenance, coverage caveats, boundaries, and preserved evidence: references/index.md.

Topic map

Representative topics: Channel & feed storage; Registry & identity; Task engine; Subagent lifecycle; Harness daemon & transport; Host integration; TUI overlay plane.
Scope and retrieval questions: references/index.md#use-this-for.
Complete capsule chooser: references/index.md#load-the-matching-source-dump.
Detailed grouped map: references/index.md#capsule-map.
Source limitations and portability boundaries: references/index.md#boundaries.

Retrieval

Open the index, choose one capsule matching the active question, and load only that capsule. Revalidate its cited source and revision before relying on it. Do not bulk-load the inventory, treat historical claims as current truth, or apply this foundation as a procedure.

---name: pi-messenger-swarm-foundationdescription: Use when building multi-agent coordination WITHOUT a central database or orchestrator process — durable agent registries with lockless name claiming, append-only event-sourced task queues with claim/dependency/cascade semantics, kafka-like feed messaging that tolerates offline recipients, subagent spawning with concurrency ceilings and crash-reconciled lifecycle tracking, or any port of the pi-messenger-swarm mesh to another agent host. Source code and direct tests are ground truth; references carry decisive excerpts and graph retrieval.---# pi-messenger-swarm: file-based multi-agent swarm coordination foundation## Foundation contractThis is a cold, source-specific foundation, not an operational procedure. It ishistorical, revision-pinned evidence rather than timeless guidance. Currentproject source, tests, requirements, and runtime behavior outrank thisprojection and decide what ships.## Provenance and revision- Source record: `pi-messenger-swarm`; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.- Recorded revision: `main@6fe429a4b74ae276a621bb72910d7926fb6b3104`.- Full provenance, coverage caveats, boundaries, and preserved evidence: `references/index.md`.## Topic map- Representative topics: Channel & feed storage; Registry & identity; Task engine; Subagent lifecycle; Harness daemon & transport; Host integration; TUI overlay plane.- Scope and retrieval questions: `references/index.md#use-this-for`.- Complete capsule chooser: `references/index.md#load-the-matching-source-dump`.- Detailed grouped map: `references/index.md#capsule-map`.- Source limitations and portability boundaries: `references/index.md#boundaries`.## RetrievalOpen the index, choose one capsule matching the active question, and load onlythat capsule. Revalidate its cited source and revision before relying on it. Donot bulk-load the inventory, treat historical claims as current truth, or applythis foundation as a procedure.

Frequently asked questions