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 agentmods add rules/agentlas-ai/agentlas-os/hephaestusgit 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/rules/agentlas-ai/agentlas-os/hephaestus)<a href="https://agentmods.dev/rules/agentlas-ai/agentlas-os/hephaestus"><img src="https://agentmods.dev/badge/rules/agentlas-ai/agentlas-os/hephaestus.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 | $0.00553 | $0.00553 |
| Opus 5 | $0.00277 | $0.00277 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
hephaestus 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 today.
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.
What it actually says
Hephaestus Network (Cursor fallback)
Cursor ships explicit /hep-network, /hep-local, /hep-cloud, and
/hep-hub commands. For /hep-network <request> or @Hephaestus <request>,
use MCP server hephaestus-network, the only host-visible Workforce MCP. Core
owns its Cloud/Hub upstream calls.
At the start of every nontrivial project turn, call
workforce.goal_context({projectDir}). If an active binding covers the ongoing
work, reuse that exact roster plus local skills before recruiting. The user
does not need to say goal.
- Author a redacted
agentlas.workforce-work-order.v1; keep private files, memory, secrets, and raw project grounding local. Use title/task plus only genuinely constraining communities/roles/skills/knowledge for semantic fit. Carry genuinely required tool capabilities, authorities, runtimes, languages, or modalities separately for post-selection host inventory and permission-receipt validation; they never rank or exclude semantic candidates. Omit unconstrained fields (absent = empty). - Call
workforce.search_candidateswith{workOrder, sourceScope: "network"}and keepfederationResult. - Author the host-LLM Selection from content/qualification evidence. Call
workforce.validate_selectionwith{workOrder, selection}and keepfederatedSelection. - Call
workforce.prepare_executionwith{workOrder, selection, federatedSelection, projectDir, goalId?}. Core requiresprojectDir, derives a goal id when needed, and automatically binds every successful preparation before execution. - Run planner/manager, workers, synthesis, and verifier as distinct calls with explicit handoffs. Claim execution only from complete receipts.
On later turns record reuse|local-only|recruit|standby|blocked through
workforce.record_goal_turn. Release a roster only after explicit whole-goal
completion/cancellation with
workforce.complete_goal(explicitCompletion=true). A 24-hour lease affects
only the next Hub charge and never ends the binding. Standby is durable
availability, not a continuously running model.
Network is registered Local + signed-in owner Cloud + public Hub. Missing
sources stay explicit. Do not call hephaestus_route, bypass Core with direct
remote search, accept deterministic staffing, or silently substitute workers.
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.
- today First seen · 47 lines · 553 tokens per session scan A 3c04400b11b4
hephaestus is a cursor rule published in the GitHub repository agentlas-ai/Agentlas-OS (1,099 stars, last pushed yesterday), licensed Apache-2.0. It adds 553 tokens to every session, about $0.0028 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.