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 instructions/intertwine/hive-orchestrator/agents-mdgit 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/instructions/intertwine/hive-orchestrator/agents-md)<a href="https://agentmods.dev/instructions/intertwine/hive-orchestrator/agents-md"><img src="https://agentmods.dev/badge/instructions/intertwine/hive-orchestrator/agents-md.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.01011 | $0.01011 |
| Opus 5 | $0.00505 | $0.00505 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
hive-orchestrator AGENTS.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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
Hive is a v2-first repository.
Start with the hive CLI, not ad hoc markdown edits or compatibility shims.
First Steps
Read skills/hive-essentials/SKILL.md before doing anything else. It explains what Hive is, how entities relate, and the key conventions.
Working Rules
- If you are just using Hive, prefer an installed
hiveCLI in a clean workspace. Checkout-only helpers in this repo are for maintainers. - Treat
.hive/tasks/*.mdas the canonical task database. - Treat
projects/*/AGENCY.mdas the narrative project document. - Read
projects/*/PROGRAM.mdbefore autonomous edits or evaluator runs. - 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.mdcurrent for the shipped v2.3 line, keepdocs/V2_4_STATUS.mdcurrent for the shipped v2.4 line, and keepdocs/V2_5_STATUS.mdcurrent for the active v2.5 draft release line. - Before substantial repo work, prefer
make workspace-status, or checkgit status --short,git worktree list,gh pr status, andhive doctor --jsondirectly. - In a fresh maintainer worktree, run
uv sync --extra devbeforepytestormake checkso the test-only dependencies are actually installed. - Build startup 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 context file. - After task, run, or memory changes, refresh projections with
hive sync projections --json. - Use
hive driver doctor <driver>andhive sandbox doctor <backend>when debugging runtime or sandbox behavior. - Before you commit, run
make check. If your slice touchesfrontend/console/**, console CI wiring, or packaged console validation, also runmake console-checkbefore review. - 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
eyesreaction 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
pushCI run onmain. A red merge commit is new blocking work, even if the PR checks were green.
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.
- 4d ago First seen · 76 lines · 1,011 tokens per session scan A 5cf926259956
hive-orchestrator AGENTS.md is an instructions file published in the GitHub repository intertwine/hive-orchestrator (23 stars, last pushed 4mo ago), licensed MIT. It adds 1,011 tokens to every session, about $0.0051 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.
Other instructions, from other repositories
codex-autoresearch AGENTS.md
Instructions for TheGreenCedar/codex-autoresearch, covering agents.md, purpose and scope, canonical sources, stable product boundaries and source and package boundaries.
OwnPilot AGENTS.md
Instructions for ownpilot/OwnPilot, covering ownpilot, architecture, key patterns, commands and tech stack.
ConsultMe CLAUDE.md
Claude Code instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
nightshift AGENTS.md
AGENTS.md instructions for orwa-mahmoud/nightshift: AI-assisted contributions are welcome. The same correctness, security, licensing, testing, and quality standards apply regardless of which tools are used.
testivai-oss CLAUDE.md
Claude Code instructions for testivai/testivai-oss, covering testivai-oss — claude code guide, repo layout, package manager, common commands and architecture — how the oss lane works.
agent-eve CLAUDE.md
Instructions for shehryarsaroya/agent-eve, covering claude.md — agent eve (né the compact, then agent transfer), 0. 🚨 hard rules, 1. what this is, 2. doc map and 3. state of play (2026-07-26).