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
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add agentlas-ai/Agentlas-OS --skill hep-stormgit clone --depth 1 https://github.com/agentlas-ai/Agentlas-OSWrote 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/skills/agentlas-ai/agentlas-os/hep-storm)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-os/hep-storm"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/hep-storm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-os/hep-storm"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/hep-storm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.02318 |
| Opus 5.5 | $0.00010 | $0.00927 |
| Sonnet 5.5 | $0.00005 | $0.00464 |
| Haiku 4.5 | $0.00003 | $0.00232 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 179 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 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.
- 1mo ago Changed · +17 lines f43a09b69d69
- 1mo ago First seen · 162 lines · 26 tokens per session scan A 637df9ff21a5
hep-storm is a skill published in the GitHub repository agentlas-ai/Agentlas-OS (1,588 stars, last pushed 4d ago), licensed Apache-2.0. It adds 26 tokens to every session and 2,318 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
yait-aichain
Build AI features in Python — an LLM call, a multi-step pipeline, the same work over many items, or an agent that uses tools (web search, page fetching, your own functions, any REST API or MCP server, a working folder), asks a human before risky actions, stays within a money budget, or pauses and resumes — on any…
yait-aichain
Build AI features in Python — an LLM call, a multi-step pipeline, the same work over many items, or an agent that uses tools (web search, page fetching, your own functions, any REST API or MCP server, a working folder), asks a human before risky actions, stays within a money budget, or pauses and resumes — on any…
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
pptagent
Create and revise editable PowerPoint presentations from a brief using HTML slide sources, rendering, and visual review. Use when the requested deliverable is a PPTX deck. The host authors the slides; text-only hosts can use an external visual reviewer.
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.