← Back to Skills Marketplace
Isolated Multi-Agent Control Plane
by
delibrately-cmyk
· GitHub ↗
· v0.1.2
334
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install cerberus-agent-foundry
Description
Production-ready multi-agent architecture kit for OpenClaw. Provides isolated per-agent workspaces, control-plane orchestration, structured task lifecycle, c...
README (SKILL.md)
Cerberus Multi-Agent Control Plane
A professional blueprint for building, operating, and governing local multi-agent teams in OpenClaw. It ships a hardened protocol stack for role isolation, task orchestration, asynchronous handoffs, and auditability.
Quick Start
- Install blueprint into target path:
bash scripts/install_blueprint.sh /path/to/your/system
- Verify task board:
python3 /path/to/your/system/scripts/taskctl.py list
- Verify mailbox:
- send:
python3 /path/to/your/system/scripts/mailboxctl.py send --task-id TSK-000 --sender team-lead --receiver coder --correlation-id CORR-001 --body "ACK protocol" - ack:
python3 /path/to/your/system/scripts/mailboxctl.py status --message-id MSG-0001 --to ACK --actor coder
- send:
What This Blueprint Provides
- Strict workspace isolation per agent (
agents/*/workspace) - Unified control plane (
control-plane/tasks,control-plane/mailbox,control-plane/logs) - Task state machine tooling (
taskctl.py) - Mailbox protocol tooling with checksum and GC (
mailboxctl.py) - Shared memory layer under control plane (
control-plane/shared-memory)
Core Rules (must enforce)
- Never use shared agent workspaces.
- Use only
control-plane/mailboxfor agent-to-agent messaging. - Team Lead is sole mailbox garbage-collection authority.
- Deploy actions require explicit human approval artifacts.
References
- Read
references/operations-checklist.mdfor rollout and audit checks. - Read
assets/blueprint/docs/protocol-v1.mdfor protocol details.
Usage Guidance
This blueprint appears coherent and local-only, but review these points before installing:
- Installation writes the blueprint into whatever path you pass to scripts/install_blueprint.sh; do not run it as root or point it at system directories unless you intend to overwrite files.
- Security is enforced by file-system layout and operational rules, not by cryptographic authentication: mailboxctl and taskctl accept an --actor parameter and will trust it. Ensure the control-plane directory has strict OS-level permissions and is only writable/executable by authorized accounts or run the tools under a confined service account.
- The event log (control-plane/logs/events.jsonl) is append-only in design, but the scripts assume the logs directory exists and that directory permissions prevent tampering; create and protect it before use.
- Test the blueprint in an isolated environment first to verify behavior (task/mailbox transitions, GC, archive behavior) and to confirm the access controls meet your needs.
- If you need stronger guarantees (non-repudiation, authenticated actions), add process-level checks (e.g., verify invoking user UID, require signed request tokens, or run services behind an authenticated daemon) rather than relying on the --actor CLI argument.
If you want, I can point out specific code lines where actor/identity is only string-checked and suggest concrete hardening changes.
Capability Analysis
Type: OpenClaw Skill
Name: cerberus-agent-foundry
Version: 0.1.2
The OpenClaw AgentSkills skill bundle is designed to establish a secure, auditable, and isolated multi-agent system. The `SKILL.md` and other markdown files (e.g., `protocol-v1.md`, agent identity files) explicitly define security boundaries, least privilege, and operational governance for the AI agents, acting as defensive prompt injections to enforce secure behavior. The `install_blueprint.sh` script performs a local copy of files. The Python scripts (`mailboxctl.py`, `taskctl.py`) handle file operations (read, write, move) strictly within the defined `control-plane` directories, implement access controls (e.g., 'team-lead' for GC), and include data integrity checks (checksums). There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or obfuscation.
Capability Assessment
Purpose & Capability
Name/description describe a local multi-agent control plane and the bundle contains templates and local CLI tooling (mailboxctl.py, taskctl.py, install script) that operate on a control-plane directory — this aligns with the stated purpose.
Instruction Scope
Runtime instructions only ask the user to copy the blueprint to a target path and run local Python scripts. The scripts operate solely on files under the installed control-plane tree and write audit events to events.jsonl. Important caveat: role/auth enforcement is convention-based (CLI arguments like --actor) and not cryptographically enforced — anyone with filesystem access or the ability to run the scripts can supply arbitrary actor values and modify files. The blueprint expects OS-level permissions / operational controls to enforce the policy.
Install Mechanism
No external downloads or package installs; install_blueprint.sh copies bundled assets into a user-specified target directory and makes scripts executable. This is low-risk from a supply-chain perspective, but the install script will write into whatever target path you provide (so installing into system directories could overwrite files if misused).
Credentials
The skill declares no environment variables or secrets and the code does not access external credentials. All operations are local filesystem reads/writes under the control-plane root; requested access is proportionate to the stated local control-plane functionality.
Persistence & Privilege
always:false and normal autonomous invocation defaults apply. The skill does not attempt to modify other skills or system-wide agent settings. Its persistence is limited to files it installs/creates under the chosen target directory.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install cerberus-agent-foundry - After installation, invoke the skill by name or use
/cerberus-agent-foundry - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.2
Rename project title to a function-first professional name; keep architecture and protocol stack unchanged.
v0.1.1
Branding and documentation upgrade: professional project positioning, clearer architecture overview, and privacy hardening (replaced personal approver label with generic human approver token).
v0.1.0
Initial release: isolated multi-agent local protocol v1 with task state machine, mailbox protocol + GC, shared-memory layer, and bootstrap scripts.
Metadata
Frequently Asked Questions
What is Isolated Multi-Agent Control Plane?
Production-ready multi-agent architecture kit for OpenClaw. Provides isolated per-agent workspaces, control-plane orchestration, structured task lifecycle, c... It is an AI Agent Skill for Claude Code / OpenClaw, with 334 downloads so far.
How do I install Isolated Multi-Agent Control Plane?
Run "/install cerberus-agent-foundry" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Isolated Multi-Agent Control Plane free?
Yes, Isolated Multi-Agent Control Plane is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Isolated Multi-Agent Control Plane support?
Isolated Multi-Agent Control Plane is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Isolated Multi-Agent Control Plane?
It is built and maintained by delibrately-cmyk (@delibrately-cmyk); the current version is v0.1.2.
More Skills