cursorrules

A set of project rules that tells AI coding agents to use the repository's Hivelore context and memory system before doing substantive work. It points agents to project context, team or personal memories, and required MCP actions.

In plain words
What is it for?
Use it in projects where agents must retrieve a briefing before editing code and record useful learnings after significant work.
Why use it?
It keeps agents aligned with decisions and knowledge already recorded for the repository. This reduces the risk of making changes based on guesses or bypassing the team's chosen workflow.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/doucs91/hivelore/cursorrules
Clone the repo
git clone --depth 1 https://github.com/Doucs91/hivelore

Made for: Cursor.

Per session 649 This file is loaded in full into every session.
When invoked 649 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 $0.00649 $0.00649
Opus 5 $0.00324 $0.00324
Sonnet 5 $0.00130 $0.00130
Haiku 4.5 $0.00065 $0.00065

Measured yesterday against content hash 7be83e569260, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

.cursorrules · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 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, invoke get_briefing with 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 call mem_relevant_to instead—but still consult Hivelore before trusting ungrounded guesses.
  • Before declaring a coding task finished, invoke the MCP prompt post_task when 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.

Git sync protocol — multi-agent coordination (MANDATORY)

Several agents and the human (Sady) work on this repo in parallel with manual pull/push. See decision 2026-05-31-decision-git-sync-protocol-multi-agent.

BEFORE a task: git pull; resolve any conflicts before touching code; verify no conflict markers remain (<<<<<<<, =======, >>>>>>>), especially under .ai/.

AFTER changing code: git commit; bump the version only if shippable package code changed (@hivelore/core, cli, mcp, embeddings), patch by default, lockstep across the 4 packages; create the tag vX.Y.Z; then git push && git push --tags. Docs-only / .ai/-only / config / CI commits → commit + push without bump or tag.

Read the full file on GitHub · 35 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. yesterday First seen · 35 lines · 649 tokens per session scan A 7be83e569260

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository Doucs91/hivelore (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 649 tokens to every session, about $0.0032 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-31.