Agentlas OS is a local-first system for creating, storing, borrowing, and running specialist AI agents and temporary agent teams through supported hosts and models. It serves people who want reusable agents that remain available across computers and model workspaces, and the catalogue contains its skills, commands, hooks, agents, instructions, plugin, and rule.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/agentlas-ai/agentlas-os/hep-storm)<a href="https://agentmods.dev/commands/agentlas-ai/agentlas-os/hep-storm"><img src="https://agentmods.dev/badge/commands/agentlas-ai/agentlas-os/hep-storm.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.03772 |
| Opus 5 | $0.00011 | $0.01886 |
| Sonnet 5 | $0.00004 | $0.00754 |
| Haiku 4.5 | $0.00002 | $0.00377 |
Grade A, and why
hep-storm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- hep-storm.body — 95% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update fallback: 자동 업데이트가 안 되면 hephaestus update를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.
/hep-storm
Drive a goal through the Stormbreaker Loop — Hephaestus' force-robust,
verifier-first execution loop — inside this Antigravity workspace. 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. Also triggered by @Hephaestus storm <goal>.
Use it for loop-worthy work: apps, sites, agents, automations, debugging, multi-step research, data/report generation — anything with files, tools, tests, or external verification. Trivial questions should be answered directly, not stormed.
Core-owned Goal + UltraCode harness
Every result includes execution_harness. Apply
execution_harness.system_prompt verbatim before planning or executing packets,
retain its prompt_sha256, and never redefine Goal mode or UltraCode mode in
this adapter. Pass live session JSON with AGENTLAS_SESSION_INVENTORY when the
host provides it; otherwise use Core's explicit host:primary fallback.
The goal is the exact text the user typed after /hep-storm.
How to run
Run the shell block below verbatim, replacing only the GOAL value with the
user's exact goal text. The block resolves the Hephaestus runner by absolute
path and runs it — there is nothing to install and nothing to add to PATH.
In an agentic runtime you are the executor: the engine gives you the verified
plan (the execution fabric); you carry it out with your own tools.
Guardrails — do NOT do any of these. They are not how this workflow works and have caused fabricated reports before:
- Do NOT diagnose
command not foundorPATH, and do NOT edit~/.zshrc. The runner is resolved by absolute path inside the block.- Do NOT claim a packet, gate, or external action succeeded without the verifier's evidence. A materialized or scheduled run is not proof.
- If the runner is genuinely missing, say so and stop. Never fabricate a fix or a run.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 218 lines · 22 tokens per session scan A 8f714ccfad92
hep-storm is a command published in the GitHub repository agentlas-ai/Agentlas-OS (1,103 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 3,772 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
dashboard-list-models
List reachable models from the dashboard registry. Usage /dashboard:list-models [annotated].
dashboard-server-tunnel-off
Disconnect the public tunnel. Usage /dashboard:server-tunnel-off.
dashboard-session-abort-all
Abort multiple running sessions (asks which). Usage /dashboard:session-abort-all.
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.
dashboard-flow-auto
Toggle autonomous mode for a session's flow. Usage /dashboard:flow-auto.
dashboard-session-rename
Rename a session. Usage /dashboard:session-rename.