Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Use when the user types /agentlas-browser , /agentlas browser, or /hep-browser for browser-required tasks, rendering pages, form flows, or visual evidence.
Use when the user types /agentlas-call , /agentlas call, or /hep-call to borrow and execute named Agentlas Hub/Cloud agents attached to the current project.
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
Use when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams.
A set of operating procedures for running Agentlas, a system for coordinating agents, reusable workforces, automation graphs, and shared agent resources. It covers candidate selection, graph creation, asset discovery, and memory rules.
Use when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release.
Use when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to run/interpret hephaestus security scan.
Use when the user types /agentlas-storm, /agentlas storm, /hep-storm, or says @Hephaestus storm to drive a goal through the force-robust Stormbreaker loop with real Agentlas specialists.
Use when the user types /agentlas-upload, /agentlas upload, $hephaestus-upload, or /hep-upload to scan, gate, and publish an agent/team package to Agentlas Cloud (private) or Agentlas Hub (public).
Use when the user types /hep-cloud or /agentlas-cloud, or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub.
Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion.