By ekson73
MAOS (Multi-Agent OS) - Coordination Framework for AI Agents with Orchestration, Sentinel Protocol, Worktree Governance, Status Maps, Forge Meta-Agent, Governance Protocols
Slash commands for the multi-agent-os plugin. Commands are auto-discovered by Claude Code from this directory.
Display human-readable status of the agentic system (git + agents + sentinel + locks) using Status Map templates. Renamed from `status` (v1.5.1) to avoid collision with Claude Code built-in `/status`.
Forge a raw intent into the optimal reusable agentic-tool — research pre-existing internal+external solutions first (DRY), decide the best artifact TYPE (prompt/skill/command/agent/mcp/plugin/marketplace/rule), name it via 5-axis rigor, make it AI-agnostic + multi-agentic, then forge + save (operator-confirmed). Thin wrapper over the `agentic-tool-forge` skill. Genesis stage of the agentic-tool lifecycle.
Decide whether and HOW to take on a candidate tool that already exists (external repo/MCP/plugin/skill or internal proposal) — understand → research similars → compare/cross → validate viability → DECIDE among install/create-internally/absorb/adapt/sub-agent/abandon/defer-HITL → (gated) governed install. Thin wrapper over the `agentic-tool-intake` skill. The ADOPT stage of the agentic-tool lifecycle.
Ultra-fast parallel web research using sub-agents for 5-10x speedup
> **Single SSOT** for the autonomy posture of the cowork-team delivery agents
Agent definitions for the multi-agent-os plugin. These define specialized personas that can be spawned by the orchestrator.
Maher Saba thinking archetype — Apple VP of Engineering. Use when you need engineering excellence thinking, integration craftsmanship, pixel-perfect execution, or hardware-software polish at Apple-grade quality.
Elon Musk thinking archetype — Tesla/SpaceX/xAI founder. Use when you need first-principles thinking, 10x ambition, questioning every assumption, vertical integration strategy, or extreme velocity.
Agile product & delivery lead — composite of the product-management roles (Product Owner · Product/Project Manager · Scrum Master · Business Analyst). Use for backlog grooming, user-story authoring (INVEST), acceptance criteria + DoR/DoD, prioritization (MoSCoW/RICE/Eisenhower), sprint facilitation, requirements elicitation/analysis, and stakeholder framing. Composite by design (Gordian) — one delivery-leadership lens, not four agents.
Analyze tasks and recommend optimal sub-agent(s) for execution
Use when about to spawn a subagent/skill/task (Task tool, Agent tool, /command). Defines 6 decision criteria (decomposable/specialist-exists/audit-capacity/score≥MEDIUM/not-HUMAN-DOMAIN/time-budget), 10 mandatory briefing components (context/scope/motivation/purpose/objective/DoR/DoD/deliverables/feedback-loops/constraints), accountability preservation (parent NEVER delegates accountability — only execution; "delegating does not waive the responsibility received"), recursion ≤2, parallel ≤3. Harmonizes the agentic-inheritance principle (tree-returns-to-root · subordinate-is-parent's-full-responsibility · audit-output · zero-drift). Cross-vendor AAIF.
Generic, vendor-neutral session-observability engine (ASH — Agentic Session Harness). Per-session journals capturing goal · tasks · decisions[] · sources · transcript_hash, plus a decision-audit (why the agent decided X, spec_alignment drift). Ships CLIs (agentic-walkthrough timeline · agentic-decisions audit report · agentic-decide capture · agentic-reindex backfill) + SessionStart/Stop hooks. Use when you need an auditable record of what an agent did and WHY across sessions. Promoted from a host product 2026-06-02 (Layer-1 community engine).
Use when you need to evaluate, test, score, benchmark, or QA an agentic-tool (a skill/SKILL.md, agent, subagent, slash-command, prompt, or MCP-tool) — e.g. "is this skill any good?", "does this skill actually trigger?", "test this agent", "did my edit regress the skill?", "compare these two skill versions", "score this command". Produces a behavioral eval report; does NOT author or modify the tool.
Use when you want to turn a raw intent/instruction into a REUSABLE agentic-tool — e.g. "turn this into a skill", "forge an agentic-tool for X", "make this a recurring command/agent", "convert these instructions into a tool", "criar um agentic-tool para …", "research then build the best tool for …". Researches pre-existing internal + external solutions FIRST (DRY), decides the OPTIMAL artifact TYPE among {prompt · skill · command · agent/subagent · mcp · plugin · marketplace · rule/hook}, names it (delegating to `anima` when present, else 5-axis inline fallback), makes it AI-agnostic + multi-agentic, then forges + saves it (operator-confirmed). The genesis stage of the agentic-tool lifecycle (forge → evaluate → train → operate → deprecate). Hands off to agentic-tool-evaluator + -trainer. Cross-vendor AAIF (Claude / Cursor / Codex / Copilot / Gemini / Aider).
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Runs pre-commands
Contains inline bash commands via ! syntax
A comprehensive Claude Code plugin for orchestrating AI agents in software development workflows.
/mvv command for one-shot executionPlugin name vs repo name: the repository is
multi-agent-os; the plugin is namedmaos(see.claude-plugin/plugin.json). Install and reference it asmaos. Skills/commands surface namespaced as/maos:<name>(e.g./maos:orchestrator,/maos:auto-pilot).
Plugin management runs inside a Claude Code session via the /plugin command (not a shell claude plugins subcommand):
/plugin marketplace add ekson73/eko-claude-plugins
/plugin install maos@eko-claude-plugins
/reload-plugins
Then run /plugin (Installed tab) to confirm, and /help to see the /maos:* skills. Need to update later? /plugin marketplace update eko-claude-plugins.
git clone https://github.com/ekson73/multi-agent-os.git
claude --plugin-dir ./multi-agent-os # load for this session
claude plugin validate ./multi-agent-os # validate the manifest
--plugin-dir may be repeated to load several plugins and takes precedence over an installed copy of the same name (handy for testing local changes). See Self-Referential Usage.
To make maos available to everyone on a repository, add to that project's .claude/settings.json (collaborators are prompted to install when they trust the folder):
{
"extraKnownMarketplaces": {
"eko-claude-plugins": {
"source": { "source": "github", "repo": "ekson73/eko-claude-plugins" }
}
},
"enabledPlugins": ["maos@eko-claude-plugins"]
}
CLI equivalent (writes project scope): claude plugin install maos@eko-claude-plugins --scope project. Full schema: Plugin settings.
npx claudepluginhub ekson73/multi-agent-os --plugin multi-agent-osTask distribution, agent coordination, progress monitoring - executes plans via subagents. Requires AI Maestro for inter-agent messaging.
Multi-agent coordination with agent-swarm MCP
Intelligent orchestration platform for AI coding tools — routes tasks to the best model, learns from outcomes, and enforces quality through multi-model consensus. 46 MCP tools for agent management, research, memory, consensus voting, codebase intelligence, and a full dev pipeline.
Agent-optimized development orchestrator with parallel task execution and workflow enforcement
This skill should be used when the model's ROLE_TYPE is orchestrator and needs to delegate tasks to specialist sub-agents. Provides scientific delegation framework ensuring world-building context (WHERE, WHAT, WHY) while preserving agent autonomy in implementation decisions (HOW). Use when planning task delegation, structuring sub-agent prompts, or coordinating multi-agent workflows.
Portable, vendor-agnostic agent harness for project-specific skills, workflows, and agent teams aligned with your codebase, conventions, and engineering standards.