Menu
Control the orchestrator stack lifecycle from Hermes via a thin wrapper over the existing stack launcher.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Process research URLs (papers, blogs, repos) through a structured intake pipeline. Extracts claims, deduplicates against a persistent index, cross-references existing work, expands literature, updates active handoffs, proposes handoff stubs, and produces a structured report. Use when ingesting new research material into the EPYC compendium.
Index the EPYC orchestrator x_* request overrides exposed through Hermes command skills.
Lint, query, and maintain the project knowledge base. Use when auditing KB health, searching for compiled knowledge, or checking governance hygiene. Do not use when ingesting new research (use research-intake).
Use when reviewing a diff, commit, PR, dependency change, agent/tool change, or codebase surface for security risk. Runs a two-pass STRIDE + OWASP Top 10 + OWASP LLM + supply-chain review with exploit-path-gated findings and P0-P3 severity.
Cap or restore the escalation tier for this conversation. Controls how far the orchestrator can escalate from frontdoor to specialist models.
Disable REPL code execution for this conversation. Forces direct text responses only — no Python/shell execution.
| name | stack |
| description | Control the orchestrator stack lifecycle from Hermes via a thin wrapper over the existing stack launcher. |
| version | 1.0.0 |
| metadata | {"hermes":{"tags":["orchestrator","stack","launcher"]}} |
Use /stack when you want Hermes to forward stack lifecycle actions directly to
the existing orchestrator launcher without inventing routing logic or runtime
glue. This command is a no-inference wrapper around
/mnt/raid0/llm/epyc-orchestrator/scripts/server/orchestrator_stack.py and
exposes the launcher’s status, start, stop, and reload commands as-is.
/stack status - Show stack state and running components/stack start - Start the stack with the launcher defaults/stack start --hot-only - Start only HOT models/stack start --include-warm ROLE... - Include specific WARM roles/stack start --only ROLE... - Start only the listed roles/stack start --dev - Start the launcher’s dev configuration/stack stop --all - Stop all managed components/stack stop COMPONENT... - Stop specific components/stack reload COMPONENT... - Reload specific components in place| Field | Value |
|---|---|
| Type | Local Hermes command wrapper |
| Launcher | /mnt/raid0/llm/epyc-orchestrator/scripts/server/orchestrator_stack.py |
| Invocation | python3 /mnt/raid0/llm/epyc-orchestrator/scripts/server/orchestrator_stack.py <command> [args...] |
| Commands | status, start, stop, reload |
| Scope | Orchestrator API, model servers, and other managed stack components |
| Hermes command | Launcher command | Notes |
|---|---|---|
/stack status | status | Read-only status inspection |
/stack start ... | start ... | Forwards launcher flags verbatim |
/stack stop ... | stop ... | Use --all or explicit component names |
/stack reload ... | reload ... | Requires one or more component names |
orchestrator_stack.py; do not infer or rename components.