hybridmind AGENTS.md

A project instruction file for HybridMind, a local service that combines several search methods over an SQLite database and explains what it retrieved and why. It sets the rules an agent must follow before changing the code.

In plain words
What is it for?
Understanding HybridMind’s architecture, following its cold-start steps, preserving its data indexes, running the offline test suite, and avoiding unsupported research claims.
Why use it?
It gives contributors a reliable starting point and helps prevent changes that conflict with the project’s architecture, research limits, or required checks.

Instructions file for CodexOpenCode

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 instructions/a3ro-dev/hybridmind/agents-md
Clone the repo
git clone --depth 1 https://github.com/a3ro-dev/hybridmind

Made for: Codex, OpenCode.

Per session 2,641 This file is loaded in full into every session.
When invoked 2,641 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.02641 $0.02641
Opus 5 $0.01321 $0.01321
Sonnet 5 $0.00528 $0.00528
Haiku 4.5 $0.00264 $0.00264

Measured 2d ago against content hash 764f81b403b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hybridmind 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 2d 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.

AGENTS.md · 179 lines

How it starts

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

HybridMind — agent entry point

Updated: August 2026. Read top to bottom before changing anything; it is short on purpose. README.md is the human-facing front door; this file is the working contract for anyone editing the code.

What this is

HybridMind is a local dense + sparse + graph retrieval service for AI-memory experiments: FastAPI over an authoritative SQLite store, with FAISS HNSW, BM25/BM25S, and NetworkX indexes derived from it. It is built to show what it retrieved, why, and whether that evidence helped.

It is not a transformer KV-cache replacement and not a validated 10M–100M-token context system. Those are preregistered research targets governed by docs/RETRIEVAL_RESEARCH_PROTOCOL.md. Do not let claims drift: the honest-status table is PHASE_IMPLEMENTATION_STATUS.md, and the research evidence ledger is docs/research/design-space-experiment-program.md.

Cold start

.\.venv\Scripts\Activate.ps1            # .venv only, never system Python
pip install -r requirements.txt         # pnpm only inside memorybench/
pytest tests/ -q                        # full offline suite (~400 tests, zero provider calls)
python -m compileall -q main.py config.py api engine storage models cli sdk mcp_server scripts benchmarks tests verify
  • The offline suite makes zero provider calls. If your change needs one, see rule 5 below first.
  • make test / make compile wrap the same checks (make verify runs the legacy opt-in suite separately).
  • API: python -m uvicorn main:app --host 127.0.0.1 --port 8000. Startup does not wake remote providers by default.
  • Arriving mid-stream? Read docs/CURRENT_STATE.md (and update it when you finish; see Covenants).

Load-bearing map (do not break casually)

Path Role Breakage radius
config.py Single configuration source of truth Every subsystem reads it; add fields here, never raw os.getenv
storage/sqlite_store.py Authoritative store (SQLite/WAL), bitemporal fields Schema/write-path changes need migration thinking
storage/vector_index.py, bm25_index.py, graph_index.py Derived rebuildable indexes Must stay rebuildable-from-SQLite; never authoritative
storage/mindfile.py .mind snapshot publish/restore validation Security-sensitive path/checksum/semantic gates
engine/hybrid_ranker.py Candidate generation, temporal filtering, RRF fusion, optional rerank stages Retrieval semantics + measured numbers depend on exact behavior
engine/fusion.py RRF implementation (k=60, weight validation) Fusion contract
engine/embedding.py, provider_policy.py Remote-only native 4096-d embeddings; endpoint-bound keys Fail-closed contract, rule 3/4
engine/llm_client.py (+ llm.py, runpod_llm.py) Centralized LLM policy chain Provider routing/spend discipline
main.py + api/*.py App assembly, security middleware, routers Auth/rate/limit logic lives in main.py ASGI middleware
eval_ledger.py, eval_common.py, eval_stats.py, eval_*.py Evaluation ledgers, prompts, statistics Recorded numbers must stay interpretable/comparable
scripts/preflight.py Default-deny live-provider admission gate Spend safety
memorybench/src/providers/hybridmind/index.ts Benchmark harness provider (gitignored tree; these two files tracked) Contract test: experiments/harnesses/memorybench_provider_contract.test.ts

Read the full file on GitHub · 179 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. 2d ago First seen · 179 lines · 2,641 tokens per session scan A 764f81b403b1

Subscribe to this mod's changes

hybridmind AGENTS.md is an instructions file published in the GitHub repository a3ro-dev/hybridmind (5 stars, last pushed 7d ago), licensed MIT. It adds 2,641 tokens to every session, about $0.0132 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.

Related

Other instructions, from other repositories

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

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

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

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,345 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

next.js 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