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/linggen/linggen-memory/claude-mdgit clone --depth 1 https://github.com/linggen/linggen-memoryWrote 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/linggen/linggen-memory/claude-md)<a href="https://agentmods.dev/instructions/linggen/linggen-memory/claude-md"><img src="https://agentmods.dev/badge/instructions/linggen/linggen-memory/claude-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.00728 | $0.00728 |
| Opus 5 | $0.00364 | $0.00364 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
linggen-memory CLAUDE.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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions
Purpose
linggen-memory is the default memory-skill backend for Linggen — a standalone Rust binary (ling-mem) that implements the Memory_* tool family (add, search, list, update, delete, forget) over a LanceDB store with semantic retrieval.
Specs for this repo:
doc/product-spec.md— features, user-facing behavior, scenariosdoc/tech-spec.md— schema, storage, CLI contract, release processDESIGN.md— rolling locked-decisions log (what was chosen and why)
The main Linggen repo owns the integration side (see ../linggen/doc/memory-spec.md and ../linggen/doc/skill-spec.md for the contract this binary must satisfy).
Status
- Branch:
main— commit & push directly onmain, never branch. The archived code-indexing tool is preserved at thev0-legacytag.
Scope
In scope for this repo:
- LanceDB store + embedding pipeline
- CLI subcommands on
ling-mem - (out-of-scope: HTTP daemon + webpage — lives in the memory skill wrapper)
- Platform release binaries (cross-compile via GitHub Actions)
- All docs under
doc/about the binary itself
Out of scope (lives in ../linggen/):
- Linggen core's
provides:field and Memory_* tool dispatch - Core-prompt injection (the engine loads
tier=corerows at session start — there is noidentity.md/style.mdmarkdown substrate; that cutover shipped) - Spec docs for the Linggen-memory integration contract (
linggen/doc/memory-spec.md)
Working rules
- Single-crate discipline. Don't re-introduce a workspace or sub-crates. Modules under
src/<name>/are the unit of organization. - Commit per sub-step. Each checklist item / sub-step in
~/.claude/plans/memory-system-rebuild.mdgets its own commit (e.g. the Phase 1a substeps each landed as one commit: addupdated_atfield, bump on update, episodic evict + tier-core query, retune dedup threshold). Build + relevantcargo testgreen before each commit. - Don't edit
v0-legacy. Tag is immutable; legacy source isgit checkout v0-legacyaway. - Preserve release tooling.
scripts/build-*.sh, signing config, and CI live through the refactor. - Dependency policy. Use current major versions;
thiserroris 2.x. LanceDB + Arrow must be a compatible triple — track the lance 0.39 × rustc 1.94 recursion-limit issue separately. - CLI is primary. All features must be reachable via
ling-memsubcommands. TheMemory_*tool-namespace dispatch in Linggen is sugar; the CLI must be complete on its own so Claude Code (Bash-only) can use it.
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 · 46 lines · 728 tokens per session scan A 0540558caba0
linggen-memory CLAUDE.md is an instructions file published in the GitHub repository linggen/linggen-memory (108 stars, last pushed 2d ago), licensed MIT. It adds 728 tokens to every session, about $0.0036 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
plur CLAUDE.md
Instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.
mentedb copilot-instructions.md
Instructions for nambok/mentedb, covering mentedb development instructions, project overview, workspace structure, build, test, and lint and key types.
dense-mem AGENTS.md
Instructions for markhuangai/dense-mem, covering dense-mem repository guidance, project context, architecture decision records, current stack and target architecture.
EGC copilot-instructions.md
Copilot instructions for Fmarzochi/EGC, covering copilot instructions for egc, repository conventions, readme and translations, code review priorities and egc project memory.
dakera-cli CLAUDE.md
Instructions for Dakera-AI/dakera-cli, covering dakera-cli, key commands, architecture and conventions.
pos CLAUDE.md
Instructions for xcota/pos, covering personal os, rules, memory, budget and hard rules.