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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OSnpx agentmods add skills/agentlas-ai/agentlas-os/hephaestus-networkWrote 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/hephaestus-network)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-os/hephaestus-network"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/hephaestus-network/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/hephaestus-network"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/hephaestus-network.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.00075 | $0.05022 |
| Opus 5.5 | $0.00030 | $0.02009 |
| Sonnet 5.5 | $0.00015 | $0.01004 |
| Haiku 4.5 | $0.00007 | $0.00502 |
Grade A, and why
hephaestus-network 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 16d 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hephaestus Agent Workforce Network
The active host LLM staffs the task. Agentlas Core federates content menus from registered Local, owner Cloud, and public Hub inventory. No source and no deterministic layer is the decision-maker or a server-side LLM executor.
Source scopes are exact:
network: Local + Cloud + Hub;local: registered Local packages only;cloud: the signed-in owner's Cloud packages only;hub: public Hub packages only.
Before an unpinned search uses the Local source, Core refreshes every active
registered source folder and creates a new immutable release when its safe
content snapshot changed. This is discovery freshness; a prepared or
goal-bound roster remains pinned to its exact release. network reindex is a
rebuildable card-cache operation and is not required to refresh a registered
Local release. New folders still require explicit local-register.
Public demos and distribution proof use explicit hub scope. They must not use
private Local/Cloud inventory as evidence of public availability.
Resolve the runner and sign in
Network can query owner Cloud and public Hub inventory, so establish the same saved Agentlas session before staffing:
RUNNER=""
for c in \
"$HOME/.agentlas/runtime/current/bin/hephaestus" \
./bin/hephaestus
do [ -x "$c" ] && RUNNER="$c" && break; done
if [ -z "$RUNNER" ]; then
for cache in \
"$HOME/.claude/plugins/cache/agentlas-core-engine/hephaestus" \
"$HOME/.codex/plugins/cache/agentlas-core-engine/hephaestus"; do
newest="$(ls -d "$cache"/*/bin/hephaestus 2>/dev/null | sort -V | tail -1)"
[ -n "$newest" ] && [ -x "$newest" ] && RUNNER="$newest" && break
done
fi
if [ -n "$RUNNER" ] && [ "${HEPHAESTUS_AUTH_AUTOPOPUP:-1}" != "0" ]; then
"$RUNNER" auth ensure >/dev/null 2>&1 || true
fi
The browser opens only when no reusable local sign-in exists. In CI or another
headless environment, set HEPHAESTUS_AUTH_AUTOPOPUP=0.
Required MCP sequence
First confirm the typed tool menu contains workforce.preflight_work_order and
that its _meta.protocolVersion is at least 2026-08-20.1. If the tool is
absent, the host is still attached to a preflight-less runtime. Do not fall back
to model-authoring the strict wire WorkOrder and do not retry the same invalid
call. Return the machine-readable boundary
workforce_protocol_upgrade_required; let the runtime's normal verified
auto-update finish, then reload the host/MCP session. An explicit
hephaestus hep-update remains an operator action, never an implicit skill
side effect.
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.
- 16d ago Changed · +42 lines b0cf257cf6fc
- 28d ago Changed · +8 lines 19abce44e3e9
- 1mo ago Changed · +5 lines 78ad1e66b1a4
- 1mo ago First seen · 356 lines · 75 tokens per session scan A 9cde3abf0c05
hephaestus-network is a skill published in the GitHub repository agentlas-ai/Agentlas-OS (1,588 stars, last pushed 3d ago), licensed Apache-2.0. It adds 75 tokens to every session and 5,022 once invoked, about $0.0003 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-08-30.
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.
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-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…
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.