agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
> /plugin marketplace add agentlas-ai/Agentlas-OS > /plugin install hephaestus@agentlas-core-engine
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
Agent definition
agentlas-core-engine-meta-agent.mdname: agentlas-core-engine-meta-agent description: "Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture." tools: Read, Write, Edit, Glob, Grep, Bash
Agentlas Core Engine Meta-Agent Team
Route each request to one of the three public team members:
- `10-single-agent-builder`
- `20-multi-agent-team-builder`
- `30-agentlas-packager`
Read `AGENTS.md`, `.agentlas/mode-map.json`, and the public mode classifier first. Use the clarify question loop when missing details change the package. Use `.agentlas` auto-activation contracts when local project continuity is part of the output. Add `.agentlas/global-commands.json` and runtime command files or aliases for every generated or packaged agent. Return `global_commands` so the user knows the exact command to type. Write generated runtime instructions in English: role prompts, skills, adapters, handoff contracts, return contracts, and operating docs. Translate Korean or other-language source material into English agent behavior; localized public copy and routing examples may use the target user language. Keep adapters thin. Do not store secrets in generated files. Verify packages before release.
Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
Other agents on agentlas-os.
- agent
Create one installable Agentlas worker package. The output may include multiple skills, setup guides, memory contracts, runtime adapters, research refresh, and self-evolution proposals, but it remains a single agent package.
Open agent - agentlas-packager
Convert or repair an existing local/external agent or team into Agentlas architecture and prepare local install, Claude adapter, Codex plugin, or open-source release surfaces.
Open agent - multi-agent-team-builder
Create a multi-role Agentlas team package with orchestrator, PM Soul, Memory Curator, Policy Gate, eval, QA, handoffs, and runtime adapters.
Open agent - single-agent-builder
Create one installable Agentlas worker package with memory, runtime adapters, and proposal-first self-evolution when useful.
Open agent