Swarm Workflow Protocol
v1.0.0Multi-agent orchestration protocol for the 0x-wzw swarm. Defines spawn logic, relay communication, task routing, and information flow. Agents drive decisions...
⭐ 0· 90·1 current·1 all-time
by@0x-wzw
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (swarm orchestration, spawn/relay/task routing) match the shipped artifacts: SKILL.md documents spawn logic, relay endpoints, task lifecycle and file locations; README and skill.json are consistent. There are no unrelated binaries, config paths or credentials requested.
Instruction Scope
SKILL.md instructs agents to communicate with a relay at http://localhost:18790 and to read/write to local memory paths (memory/...). That is within the described purpose, but the instructions also encourage autonomous spawning and continuous agent-driven decisions — which increases runtime power and risk if the relay or spawn behavior is misused. The doc contains a hard-coded auth header value (x-auth-token: agent-relay-secret-2026) rather than referring to a declared credential.
Install Mechanism
This is an instruction-only skill with no install spec; only a small validate.sh script is included. No downloads, package installs, or archive extraction are present. Low install risk.
Credentials
The skill declares no required environment variables or credentials, which is consistent. However, the SKILL.md (and README examples) embed a static auth token for the local relay. Hard-coded secrets in documentation are a sensitive operational detail — they should be treated as defaults/examples and rotated or moved to a secure env var in practice.
Persistence & Privilege
The skill does not request always:true and uses default autonomy settings (user-invocable, model invocation allowed). It does not modify other skills or system-wide config in the provided files.
Assessment
This skill looks like what it says: a protocol for multi-agent orchestration that uses a local relay endpoint. Before installing or enabling it: 1) Verify the relay process on localhost:18790 is expected and secured — the SKILL.md contains a hard-coded token (x-auth-token: agent-relay-secret-2026); treat that as a default/example and prefer moving tokens into secure environment variables. 2) Decide whether you want agents to be able to spawn other agents autonomously — the protocol explicitly encourages agent-driven decisions and spawning, which increases the blast radius if misconfigured. 3) Confirm you trust the publisher (source is unknown); consider reviewing the repository linked in skill.json or running the included validate.sh locally to inspect SKILL.md. 4) Monitor network and process activity after enabling the skill (e.g., local relay traffic, created files under memory/) and enforce least privilege for any relay service. If you need a stricter posture, require user approval before any spawn/relay actions or patch the SKILL.md to require an env var for the relay token.Like a lobster shell, security has layers — review code before you run it.
latestvk973kvj9f465w571kbm81cbn5583a1nk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.