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 intertwine/hive-orchestrator --skill hive-work-loopgit clone --depth 1 https://github.com/intertwine/hive-orchestratorWrote 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/intertwine/hive-orchestrator/hive-work-loop)<a href="https://agentmods.dev/skills/intertwine/hive-orchestrator/hive-work-loop"><img src="https://agentmods.dev/badge/skills/intertwine/hive-orchestrator/hive-work-loop/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/intertwine/hive-orchestrator/hive-work-loop"><img src="https://agentmods.dev/badge/skills/intertwine/hive-orchestrator/hive-work-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Excessive Agency · line 80 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00049 | $0.01671 |
| Opus 5.5 | $0.00020 | $0.00668 |
| Sonnet 5.5 | $0.00010 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
hive-work-loop 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hive Work Loop
This is the core cycle for getting work done in Hive. It covers the full path from finding a task to promoting the result.
The Loop
find ready work → build context → claim → launch run → monitor
→ handle approvals → finish (evaluates + promotes) → release
1. Find Ready Work
hive next --json # recommended next task
hive task ready --json # full ready queue
hive task ready --project-id <project-id> --json # scoped to one project
hive next returns the highest-priority unblocked task. It respects dependency constraints and expired claims.
If the queue is empty, check why:
hive deps --json # shows blockers
hive task list --json # shows all tasks regardless of status
2. Build Context
hive context startup --project <project-id> --task <task-id> --json
This compiles a startup bundle: task description, acceptance criteria, project mission, API docs, code examples, dependency snapshot, and previous notes.
For a saved markdown bundle (from a repo checkout):
make session PROJECT=<project-id>
3. Claim the Task
hive task claim <task-id> --owner <your-name> --ttl-minutes 30 --json
Claims are time-limited leases. Other agents can see who holds what. Always claim before starting work so you do not collide.
Read PROGRAM.md before proceeding with autonomous work:
cat projects/<project-id>/PROGRAM.md
4. Launch a Run
For governed execution (recommended):
hive work <task-id> --owner <your-name> --json
hive work does several things:
- Creates a git worktree with an isolated branch
- Compiles startup context
- Checkpoints workspace state
- Launches the driver
- Emits a run record
For more control over driver and model:
hive work <task-id> --owner <your-name> --driver codex --model gpt-4 --json
For batch mode (no interactive follow-up):
hive run start <task-id> --driver local --json
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 First seen · 209 lines · 49 tokens per session scan A 2fbe6ea57bce
hive-work-loop is a skill published in the GitHub repository intertwine/hive-orchestrator (22 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,671 once invoked, about $0.0002 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
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
paperclip-distill
Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator.