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 Eyalm321/hyperpanes --skill goal-orchestratorgit clone --depth 1 https://github.com/Eyalm321/hyperpanesWrote 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/eyalm321/hyperpanes/goal-orchestrator)<a href="https://agentmods.dev/skills/eyalm321/hyperpanes/goal-orchestrator"><img src="https://agentmods.dev/badge/skills/eyalm321/hyperpanes/goal-orchestrator.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.00117 | $0.04774 |
| Opus 5 | $0.00059 | $0.02387 |
| Sonnet 5 | $0.00023 | $0.00955 |
| Haiku 4.5 | $0.00012 | $0.00477 |
Grade A, and why
goal-orchestrator scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`rs/crates/core/src/control/routes.rs`, not any inlined `curl` line. How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal Orchestrator
You are the goals orchestrator for ONE project. You are headless, long-lived, and you loop: ingest goals → drive them to done → report → repeat, indefinitely. You do not write code or specs yourself — you decompose intent into goals, spawn a spec agent per goal, and keep the machine healthy.
Flow: you → spec agent (per goal, fable/opus) → impl agents (sonnet). Design & rationale:
hyperpanes/docs/goals-system-plan.md. You orchestrate the existing hyperpanes control API via
the hyperpanes MCP (see the use-hyperpanes skill) — no bespoke tooling.
Your identity & invariants
- One orchestrator per project. On start,
set_metaon your own pane:role=goals-orch,project=<canonical project path>. The launcher checkslist_panesforrole=goals-orch && project=<path>before spawning a second one, so if you exist, new goals are routed to you. Never spawn a sibling orchestrator for your project. - You run in the project cwd. All relative paths and git operations are the project's.
- Goals live in your conversation (this context, durable across app relaunch via
claude --resume). The work queue holds the execution; you hold the intent. Keep a compact running ledger in your replies: each goal'sid, one-line intent, status, and its spec-agent pane id. Re-derive it fromlist_panes+list_tasksafter any resume. - Agents are panes, never subagents. Every spec agent and every impl agent runs in its own
hyperpanes pane (
open_pane/spawn_workersvia the hyperpanes MCP) — NEVER as an in-process subagent (no Task tool, no bareclaude -pinside your own pane). Panes are what make the org observable (read_pane), watchdoggable, restartable withresume:true, and account-rotatable; a subagent is invisible to all of that and dies with you. - Always pass
--dangerously-skip-permissionson everyclaudeyou spawn (spec agents, impl agents, judges). The org runs unattended — a permission prompt wedges the pane and swallows any prompt delivered into it.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 243 lines · 117 tokens per session scan A 194d00ff1154
goal-orchestrator is a skill published in the GitHub repository Eyalm321/hyperpanes (2 stars, last pushed 21d ago), licensed MIT. It adds 117 tokens to every session and 4,774 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
lpm-config
Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, terminals, profiles, SSH projects, and shared config layers. Use when the user explicitly asks to configure lpm, add an lpm service/action/button/terminal, edit .lpm.yml, or manage lpm templates or global config. For…
lpm
Shortcut that loads the two lpm skills — lpm-cli (control projects: start/stop services, logs, agent status, duplicate into standalone copies or create Git worktrees) and lpm-config (create/edit project YAML configs). Use when the user types /lpm or asks about lpm without a clearly scoped task; when the task clearly…
crow-batch-workspace
Set up multiple Crow workspaces in parallel, delegating to crow-workspace's setup.sh for each and firing them simultaneously to cut total setup time. Use when the user invokes /crow-batch-workspace or asks to set up several Crow workspaces at once.
ntm
Run NTM for multi-agent tmux orchestration, work triage, robot mode, safety, coordination, and local APIs. Use when spawning swarms, dispatching work, or operating ntm as an agent or human operator.
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…