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/janbjorge/rekal/agents-mdgit clone --depth 1 https://github.com/janbjorge/rekalWrote 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/janbjorge/rekal/agents-md)<a href="https://agentmods.dev/instructions/janbjorge/rekal/agents-md"><img src="https://agentmods.dev/badge/instructions/janbjorge/rekal/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.01640 | $0.01640 |
| Opus 5 | $0.00820 | $0.00820 |
| Sonnet 5 | $0.00328 | $0.00328 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
rekal 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 3d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rekal: Agent Instructions
What this project is
rekal is a Model Context Protocol (MCP) server that gives LLMs persistent long-term memory.
It uses hybrid search (FTS5 + vector + recency) in a single SQLite file.
Python 3.11+, installed via pip install rekal, runs as a stdio MCP server.
Architecture
MCP Client
│ stdio (JSON-RPC)
│
mcp_adapter.py ← create_server() factory, lifespan (creates/closes DB)
│
└── tools/core.py ← the 3 tools (build_context, store, delete) + register()
│
sqlite_adapter.py ← SqliteDatabase @dataclass, ALL SQL lives here
│
├── SQLite (memories: content, project, tags, timestamps)
├── FTS5 (full-text index, auto-synced via triggers)
└── sqlite-vec (vector index)
Key rules
SqliteDatabaseis a@dataclassholding theaiosqlite.Connectionand ALL query methods. Every SQL statement lives here. No SQL in tool files.tools/core.pyholds the tool functions as plain async functions plusregister(mcp, readonly=...), which attaches them to a server.REKAL_READONLY=1registers recall only.mcp_adapter.pyexposescreate_server(): builds the MCPServer with the right instructions, manages lifespan, and callsregister.- The MCP surface is deliberately minimal (3 tools). Admin operations (health, export, prune, recall) belong in the CLI (
rekal/__main__.py), not new MCP tools. - No dynamic SQL. SQL strings must be static literals. No f-strings, no string concatenation, no
%formatting to build queries. Use subqueries and parameterized?placeholders instead.
Re-expansion bar
Do not restore conversations, memory links, scratch/TTL, memory types, access counters, or extra MCP tools because they sound useful. Earlier versions carried all of that; benchmarks showed the structure cost tokens (fatter payloads, fatter instructions) without earning them back. Prefer improving injection quality, bench coverage, and write hygiene (skills/CLI) first.
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.
- 3d ago First seen · 191 lines · 1,640 tokens per session scan A 55878e5a21ef
rekal AGENTS.md is an instructions file published in the GitHub repository janbjorge/rekal (53 stars, last pushed 8d ago), licensed MIT. It adds 1,640 tokens to every session, about $0.0082 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
Vault-Agent-Memory AGENTS.md
Instructions for zycaskevin/Vault-Agent-Memory, covering agent instructions for vault agent memory, common install architecture, second decision: optional features, first decision: database scope and safe agent workflow.
zen CLAUDE.md
Claude Code instructions for sheshbabu/zen, covering claude.md, development commands, build commands, dependencies and go build tags.
db-mcp copilot-instructions.md
Instructions for neverinfamous/db-mcp, covering db-mcp — copilot code review context, project overview, session context, coding standards and naming.
state-memory-mcp copilot-instructions.md
Instructions for putervision/state-memory-mcp, covering state memory (state-memory-mcp), 1. priority order, 2. when to write to the graph, 3. workflow pattern and 4. codebase seeding on initialization.
context-sync AGENTS.md
Instructions for Intina47/context-sync, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
ssh-mcp-server CLAUDE.md
Instructions for KinoThe-Kafkaesque/ssh-mcp-server, covering ssh mcp server - claude code guide, project overview, architecture, available tools and credential management.