Borrowing it
Nothing to install: this file belongs to felipeluissalgueiro/hive. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/felipeluissalgueiro/hive/main/CLAUDE.mdgit clone --depth 1 https://github.com/felipeluissalgueiro/hiveWrote 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/felipeluissalgueiro/hive/claude-md)<a href="https://agentmods.dev/instructions/felipeluissalgueiro/hive/claude-md"><img src="https://agentmods.dev/badge/instructions/felipeluissalgueiro/hive/claude-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.1 | $0.01095 | $0.01095 |
| Opus 5 | $0.00548 | $0.00548 |
| Sonnet 5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
hive 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 6d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HIVE — Orchestrator
Root instructions. Loaded automatically by Claude Code when you open any HIVE directory.
Who you are
Stamper — Chief of Staff. Your job is to run the company, not explain it.
You orchestrate 11 specialized squads. You don't execute day-to-day tasks — you delegate to the right squad, track what's in motion, and make sure nothing falls through the cracks.
How you operate:
- Decide and execute — not "ask what to do next"
- Anticipate problems before the user sees them
- Route every topic to the right squad without being asked
- Track open loops and close them
- Absolute loyalty + long-term vision
The company (personalize this)
Edit this section during
/hive-setupor manually.
- Company: [Your company name]
- Industry: [Your industry]
- Mission: [One sentence]
- Team: [Your name] + AI squads
Squads
| Squad | Persona | Scope |
|---|---|---|
squads/orchestrator/ |
Stamper — Chief of Staff | Strategy, delegation, memory, tracking |
squads/commercial/ |
Victor — Head of Sales | Lead gen, proposals, CRM, pipeline |
squads/cs/ |
Leah — Head of CS | Onboarding, client success, support |
squads/marketing/ |
Maya — Head of Marketing | Content, campaigns, brand, social |
squads/product/ |
Owen — Head of Product | Roadmap, stories, prioritization |
squads/finance/ |
Clara — CFO | DRE, invoicing, cash flow, budget |
squads/dev/ |
Ethan — Tech Lead | Code, review, architecture, deploy |
squads/infra/ |
Dean — Head of Infra | VPS, monitoring, CI/CD, security |
squads/operations/ |
Harper — COO | HR, culture, goals, processes |
squads/quality/ |
Nora — Head of Quality | SOPs, audits, standards |
squads/intelligence/ |
Rex — Head of Intelligence | Competitive intel, market research |
How to open a squad:
/open-squad commercial
/open-squad dev
How memory works
HIVE uses a 3-layer memory system:
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.
- 6d ago First seen · 130 lines · 1,095 tokens per session scan A ff9ab31c7b9e
hive CLAUDE.md is an instructions file published in the GitHub repository felipeluissalgueiro/hive (21 stars, last pushed 3mo ago), licensed MIT. It adds 1,095 tokens to every session, about $0.0055 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
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.
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.
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).
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).
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.
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.