agentmods.dev

hive-orchestrator: Instructions file for Claude Code

CLAUDE.md

hive-orchestrator CLAUDE.md is an instructions file for Claude Code from intertwine/hive-orchestrator. It costs 972 tokens per session, scanned A, original, MIT.

Repository instructions for Hive, a command-line system that coordinates project tasks and agent work. They describe where task state, project context, autonomy rules, and release status are kept.

In plain words
What is it for?
Use them when starting substantial Hive work, checking workspace health, loading project context, or maintaining release documentation.
Why use it?
They tell agents which sources to trust and which checks to run before changing the repository, reducing conflicts with the project's current state.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions Codex.

This is intertwine/hive-orchestrator's own configuration. It tells Claude Code how to work on hive-orchestrator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hive-orchestrator configures →

not rated 23 changed today A scan 972 tokens original MIT
View the source file intertwine/hive-orchestrator
Reuse

Borrowing it

Nothing to install: this file belongs to intertwine/hive-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/intertwine/hive-orchestrator/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/intertwine/hive-orchestrator

Made for: Claude Code.

Wrote 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.

agentmods badge for hive-orchestrator CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/intertwine/hive-orchestrator/claude-md.svg)](https://agentmods.dev/instructions/intertwine/hive-orchestrator/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/intertwine/hive-orchestrator/claude-md"><img src="https://agentmods.dev/badge/instructions/intertwine/hive-orchestrator/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 972 This file is loaded in full into every session.
When invoked 972 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00972 $0.00972
Opus 5 $0.00486 $0.00486
Sonnet 5 $0.00194 $0.00194
Haiku 4.5 $0.00097 $0.00097

Measured today against content hash d264c9e49832, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

hive-orchestrator CLAUDE.md 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.

CLAUDE.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE

Use Hive through the v2 substrate and CLI.

This repository is CLI-first. If you are operating here, use the commands and files below.

Working Rules

  • If you are just using Hive, prefer an installed hive CLI in a clean workspace. Repo checkout helpers are for maintainers.
  • Canonical task state lives in .hive/tasks/*.md.
  • Human project context lives in projects/*/AGENCY.md.
  • Autonomy policy lives in projects/*/PROGRAM.md.
  • If repo-local docs, skills, memory, and current git state disagree, trust current repo state and tests first, then repo-local docs and PROGRAM.md.
  • Keep docs/V2_3_STATUS.md current for the shipped v2.3 line, keep docs/V2_4_STATUS.md current for the shipped v2.4 line, and keep docs/V2_5_STATUS.md current for the active v2.5 draft release line.
  • Before substantial repo work, prefer make workspace-status, or check git status --short, git worktree list, gh pr status, and hive doctor --json directly.
  • In a fresh maintainer worktree, run uv sync --extra dev before pytest or make check so the test-only dependencies are actually installed.
  • Build context with hive context startup --project <project-id> --task <task-id> --json.
  • Use make session PROJECT=<project-id> only from a repo checkout when you want a saved startup bundle.
  • Refresh projections with hive sync projections --json after substrate changes.
  • Use hive driver doctor <driver> and hive sandbox doctor <backend> when debugging runtime or sandbox behavior.
  • Run validation appropriate to the changed surface: focused tests for narrow changes, make check for broad Python/runtime changes or required release/merge gates, and affected links/examples or documentation tests for documentation-only changes. Run make console-check for console changes. Preserve required CI and governed-run evaluation gates.
  • If you request Claude review, treat it as pending until GitHub shows a new Claude comment or review artifact on the latest PR head. An eyes reaction alone does not count as completion.
  • For maintainer-critical PRs, local Claude review is an acceptable primary or fallback review path when GitHub-managed review is delayed or ambiguous. The built-in claude -p "/review <pr-number>" flow works well for this. Summarize the resulting findings in the PR thread.
  • After merging, watch the push CI run on main. A red merge commit is new blocking work, even if the PR checks were green.

Read the full file on GitHub · 64 lines

Changes

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.

  1. today Changed · +30 tokens per session d264c9e49832
  2. 6d ago First seen · 64 lines · 942 tokens per session scan A 093dc7d98598

Subscribe to this mod's changes

hive-orchestrator CLAUDE.md is an instructions file published in the GitHub repository intertwine/hive-orchestrator (23 stars, last pushed today), licensed MIT. It adds 972 tokens to every session, about $0.0049 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-08-30.

Autonomous Agentsagentic-aiai-agentsclaudegithub-actionshuman-in-the-loop
Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens