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/doucs91/hivelore/copilot-instructionsgit clone --depth 1 https://github.com/Doucs91/hiveloreWhat 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.01435 | $0.01435 |
| Opus 5 | $0.00718 | $0.00718 |
| Sonnet 5 | $0.00287 | $0.00287 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
hivelore copilot-instructions.md 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 yesterday.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **2026-06-07-convention-vscode-cli-calls-through-runhaive** _(applies to: packages/vscode/src/extension.ts, packages/vscode/src/briefingPanel.ts, packages/vscode/src/observabilityProvider.ts)_: Raw child_process in the How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
See .ai/project-context.md for the full project context.
Memories live under .ai/memories/ (personal/team/module).
Hivelore — mandatory rules for AI agents
Installing or initializing Hivelore in this repository means the team expects AI agents to drive work through Hivelore, not bypass it.
MCP first (default — never optional unless the developer says so)
The haive MCP server must be enabled in your client. Until it is unavailable (misconfiguration report to the developer), you must use it for substantive work:
- Before you edit project source files, configs (
package.json, tooling), or workflows for the current goal, invokeget_briefingwith a short task string (and files / symbols when you know them). If project context was already refreshed in this session and you only need ranked memories, you may callmem_relevant_toinstead—but still consult Hivelore before trusting ungrounded guesses. - Before declaring a coding task finished, invoke the MCP prompt
post_taskwhen the session produced learnings or substantive changes worth capturing.
Do not treat these as nice-to-have: they are default-required for coding agents here.
Session rules
- Immediately when an approach fails (wrong API, wrong pattern, wrong assumption), call
mem_tried— do not wait until the end of the session.
Safety rules — NEVER violate these
- If
get_briefingreturns anaction_requiredlist, stop and show each item to the developer before doing anything. Use the exactdeveloper_messageprovided. Wait for explicit confirmation. - Never modify code autonomously because of a breaking change detected in another project (dependency version bump, API contract change, removed field). Always ask first.
- When in doubt about a cross-repo change: ask, don't act.
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.
- yesterday First seen · 68 lines · 1,435 tokens per session scan A 9863f16f6b2c
hivelore copilot-instructions.md is an instructions file published in the GitHub repository Doucs91/hivelore (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,435 tokens to every session, about $0.0072 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
gortex CLAUDE.md
Claude Code instructions for zzet/gortex, covering gortex, build & test, codebase overview, discovery (read once, then keep using) and llm provider (powers ask and searchsymbols assist: modes).
mcp-unity AGENTS.md
Instructions for CoderGamester/mcp-unity, covering mcp unity — ai agent guide (mcp package), purpose (what this repo is), how it works (high-level data flow), key defaults & invariants and repo layout (where to change what).
mcp-server-azure-devops AGENTS.md
Instructions for Tiberriver256/mcp-server-azure-devops: /home/tiberriver256/repos/mcp-server-azure-devops/docs/important-knowledge/azure-devops-rest-api-research.md Researching Azure DevOps REST APIs, selecting api-version, or handling Azure DevOps Server (on-prem) endpoints.
rosetta AGENTS.md
Instructions for griddynamics/rosetta: Main goal: cover E2E AI PDLC engineering workflows at foundation level for AI-First SDLC in enterprise. Top-level or orchestrator agents MUST READ docs/ARCHITECTURE.md contains technical details and guidance, and docs/CONTEXT.md - business context. Subagents - when needed.…
rails-ai-context AGENTS.md
Instructions for crisnahine/rails-ai-context, covering rails-ai-context, agent skills, issue tracker, triage labels and domain docs.
inspecto CLAUDE.md
Instructions for inspecto-dev/inspecto, covering inspecto — claude code development guide, project overview, monorepo structure, development phases (load each file as needed) and key architectural decisions.