by agentlas-ai
Open Agent OS for Claude Code, Codex, and Cursor: meta-agent builder, A2A Hub routing, local ontology, memory and security gates.
# Add to your Claude Code skills
git clone https://github.com/agentlas-ai/HephaestusHephaestus is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by agentlas-ai. Open Agent OS for Claude Code, Codex, and Cursor: meta-agent builder, A2A Hub routing, local ontology, memory and security gates. It has 79 GitHub stars.
Hephaestus's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/agentlas-ai/Hephaestus" and add it to your Claude Code skills directory (see the Installation section above).
Hephaestus is primarily written in Python. It is open-source under agentlas-ai on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh Hephaestus against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Paste this into Claude Code, Codex, Gemini CLI, Antigravity, or Cursor. Let the AI install Hephaestus and tell you which command surface is active in that tool.
Install Hephaestus Agentlas for this workspace from this GitHub repo:
https://github.com/agentlas-ai/Hephaestus
Use the latest release/instructions. If anything errors, diagnose and fix it, retry, and confirm which command surface is active in this tool.
After it finishes, tell me the three primary commands I should use:
1. create/build agents
2. borrow public Hub agents
3. use agents saved in my Agentlas Cloud
Then also tell me the two power-user commands:
4. search Cloud and Hub candidates without invoking
5. call exact agent slugs I name
6. upload agents only after asking whether I mean private Cloud or public Hub
If anything fails, read the error, fix it, retry, and confirm Claude Code,
Codex, Gemini CLI, Antigravity, and Cursor registration status.
| Job | Command | Example prompt |
|---|---|---|
| Create | /hep-build |
/hep-build create a customer support agent for Shopify refunds |
| Borrow | /hep-network |
/hep-network split this launch plan into research, copy, QA, and release agents |
| Share | /hep-cloud |
/hep-cloud use my saved finance analyst agent to review this report |
| Job | Command | Example prompt |
|---|---|---|
| Search | /hep-search |
/hep-search 시장 리포트 써야 하는데 쓸만한 에이전트 찾아줘 |
| Call | /hep-call |
/hep-call market-researcher, report-writer {시장 리포트 초안 만들어줘} |
| Upload | /hep-upload |
/hep-upload ./agents/customer-support-hq |
Fresh installs and updates prune the old visible /hephaestus chat command so
new users see the clean command surface above: three primary commands, plus
search, call, and upload utilities when they need explicit control.
/hep-build,
/hep-network, /hep-cloud, /hep-search, /hep-call, and /hep-upload
across Claude Code, Codex, Gemini CLI, Antigravity, Cursor, OpenCode, and
terminal installs./hep-upload always asks whether you mean private
Agentlas Cloud or public Agentlas Hub before it packages, publishes,
registers, or uploads anything./hephaestus-* chat command files while preserving compatibility for older
terminal callers.Hephaestus is the open core engine that makes Agentlas behave like an agent operating system instead of a one-off prompt generator. It gives developers five connected control planes:
One command, every runtime, all local:
/hep-build create a customer support agent
/hep-network borrow the right agents for this launch plan
/hep-cloud use the agent I shared to my Agentlas Cloud
/hep-search find agents for an ASO review workflow
/hep-call aso-researcher, reply-writer {draft replies for these reviews}
~/.agentlas/networking/ and never leaves the
machine without an explicit export approval./hep-build to create or repair agents,
/hep-network to borrow public Hub agents into a temporary task
force, and /hep-cloud to use agents you saved or shared through
Agentlas Cloud. Heavy users can add /hep-search to compare Cloud and
Hub candidates without invoking, and /hep-call to prepare exact
named agents. The lower-level ao, network, cards, and mcp commands
stay available for automation and debugging./hep-network requests are
decomposed only when needed, then returned as a Hub/local TF plan with
Stormbreaker packets, session hints, ontology graph paths, Local Operator
policy labels, and Memory/Playbook candidates in the receipt.The A2A upgrade is the external agent interoperability boundary. It does more than find a Hub result: it imports, exports, and gates agent-to-agent cards without leaking local project state.
agentlas-cloud ao a2a import ./agent-card.json .
agentlas-cloud ao a2a export . --agent local/10-builder
agentlas-cloud route "run the release check" --caller local/orchestrator .
AgentCard files become
ExternalAgent proposals plus capability alignment edges only. Import never
grants can_invoke, rejects malformed JSON, and caps untrusted skill lists./.well-known/agent-card.json from public fields. Private paths, local
memory behavior, raw routing-card text, and policy rationale are redacted.route --caller flag and MCP
hephaestus_route.caller_id input thread the caller into the route gate, so
blocked agent-to-agent calls stay blocked before a route is selected.Details: [docs/hephaestus-network-