hephaestus-storm
Use when the user types /hep-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.
npx skills add agentlas-ai/Agentlas-OS --skill hephaestus-storm --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Update fallback: 자동 업데이트가 안 되면 `hephaestus update`를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다. # Hephaestus Stormbreaker Loop Drive a goal through the **Stormbreaker Loop** — Hephaestus' force-robust, verifier-first execution loop. Unlike a one-shot answer or a generic parallel fan-out, Stormbreaker **routes the goal to real Agentlas specialists**, structures the work as a dependency-ordered pipeline fabric, drives each work packet as a **hardened goal loop** (it does not stall, run away, or claim false success), and **refuses to report success without evidence**. Never guess an agent yourself when this skill is active — the router or Hub decides the workforce. ## Core-owned Goal + UltraCode harness Every `hep-storm` result includes `execution_harness`. Before planning or executing any packet, apply `execution_harness.system_prompt` **verbatim** and retain its `prompt_sha256` in the goal ledger. This adapter must never redefine, summarize, or replace Goal mode or UltraCode mode with host-local wording. The adapter owns invocation only; Agentlas Core owns the execution protocol. If the host exposes live Codex, Claude Code, Gemini, local-model, or other sessions, provide their JSON a
- Core-owned Goal + UltraCode harness
- 1. Resolve the runner
- 1.5 Core project first-contact contract
- 2. Agentlas sign-in
- 3. Route and materialize the execution fabric
- 4. Branch on the route decision
- 5. Run the Stormbreaker Loop over the fabric
- 6. Loop invariants (why this beats a one-shot loop)
- 7. Hard rules
for c in \
do [ -x "$c" ] && RUNNER="$c" && break; done
if [ -z "$RUNNER" ]; then
for cache in \
done
fi
if [ "${HEPHAESTUS_AUTH_AUTOPOPUP:-1}" != "0" ]; then
printf '%s\n' "$FABRIC"What does the hephaestus-storm skill do?
Use when the user types /hep-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.
How do I install it?
Run `npx skills add agentlas-ai/Agentlas-OS --skill hephaestus-storm --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentlas-ai/Agentlas-OS, a repository with 1,165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.