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/bflabsai/clawmem-bf/agents-mdgit clone --depth 1 https://github.com/BFLabsAI/clawmem-bfWrote 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/bflabsai/clawmem-bf/agents-md)<a href="https://agentmods.dev/instructions/bflabsai/clawmem-bf/agents-md"><img src="https://agentmods.dev/badge/instructions/bflabsai/clawmem-bf/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.04690 | $0.04690 |
| Opus 5 | $0.02345 | $0.02345 |
| Sonnet 5 | $0.00938 | $0.00938 |
| Haiku 4.5 | $0.00469 | $0.00469 |
Grade B, and why
clawmem-bf AGENTS.md scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Intermittent `UserPromptSubmit hook timed out after 8s — output discarded`** → almost always the context-surfacing hook's **cold-start** (fresh Bun process + opening a large `index.sqlite` + cold OS page cache), NOT How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawMem — Agent Quick Reference
On-device retrieval-augmented memory for Claude Code, OpenClaw, and Hermes agents. Hooks auto-inject context (~90%); MCP tools cover targeted recall (~10%). TypeScript on Bun, MIT.
This file is the lean root SSOT — agent-facing essentials only. Deep reference lives in docs/ (linked throughout, indexed at the bottom). CLAUDE.md is an @AGENTS.md import; SKILL.md is the portable on-demand operating reference.
Inference at a glance
Three services — embedding, LLM (query expansion / intent / A-MEM), reranker. Default: all three as llama-server with an in-process node-llama-cpp fallback that auto-downloads on first use (works with no GPU). The bin/clawmem wrapper points at localhost:8088/8089/8090. Always run via bin/clawmem — it sets the endpoints.
Choose a stack:
- native (default) — EmbeddingGemma-300M + qmd-query-expansion-1.7B + qwen3-reranker-0.6B · ~4 GB or in-process · permissive, commercial OK · zero-config.
- z / SOTA — zembed-1 + qmd-query-expansion-1.7B + zerank-2 seq-cls sidecar · ~16 GB · CC-BY-NC-4.0, non-commercial only · best recall.
- cloud embedding — Jina/OpenAI/Voyage/Cohere · embedding only (LLM + reranker stay local) · no local GPU needed.
Landmines:
- The zerank-2 GGUF is inert — llama.cpp drops the score head → ranking silently collapses to RRF. Use the seq-cls sidecar; verify with
clawmem rerank-health(liveness ≠ correctness). -ubmust equal-bfor embedding/reranking (non-causal attention) orllama-serverasserts.- Changing embedding dimensions →
clawmem embed --force(full re-embed). CLAWMEM_NO_LOCAL_MODELS=trueto fail fast instead of silent CPU fallback.
→ Stack decision matrix + server setup: docs/guides/inference-services.md · cloud: docs/guides/cloud-embedding.md · all env vars: docs/reference/configuration.md.
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.
- 2d ago First seen · 239 lines · 4,690 tokens per session scan B 132ff6d3422b
clawmem-bf AGENTS.md is an instructions file published in the GitHub repository BFLabsAI/clawmem-bf (0 stars, last pushed 2mo ago), licensed MIT. It adds 4,690 tokens to every session, about $0.0234 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).
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.
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.
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.
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).
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.