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/wuesteon/lean-memory/claude-mdgit clone --depth 1 https://github.com/Wuesteon/lean-memoryWhat 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.01646 | $0.01646 |
| Opus 5 | $0.00823 | $0.00823 |
| Sonnet 5 | $0.00329 | $0.00329 |
| Haiku 4.5 | $0.00165 | $0.00165 |
Grade A, and why
lean-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 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
⚠️ START HERE: strategy is quality-gate → MCP launch (2026-07-08)
Approved direction: close a small, hard quality gate on the first-run experience, then launch across MCP channels (Pure A). Read before any work:
docs/superpowers/specs/2026-07-08-strategic-direction-design.md— the approved strategy (positioning, the six-item quality gate, launch plan, the six-week post-launch demand read). Non-negotiable context; do not re-derive.docs/superpowers/plans/2026-07-08-launch-quality-gate.md— the ordered implementation plan that executes the gate.
State: the former "Phase 2 suspended, fix engine then re-run benchmarks" framing
is superseded. Engine-fix backlog items 1–3 are FIXED on launch-gate
(numbers are the source of truth in bench/results/calibration/README.md):
- Escalation recalibration — endpoint-scoped coref +
prior_entitytrigger dropped (two user-approved amendments); real-turn escalation 95.9% → 14.6% at the frozen(typing=0.4, conf=0.4)operating point; goldset 10.1% → 7.6%. BET-2 revalidation PASSES all three gates. - Extraction granularity — GLiNER
DEFAULT_THRESHOLD0.1 → 0.4; 8.43 → 3.67 facts/turn. - Recency anchoring —
Memory.search(now=...)forwards search-time now (wall-clock default unchanged).
Benchmark runs (LongMemEval/LoCoMo) are DEFERRED past the MCP launch per the
spec — they are a post-launch credibility layer, not the critical path. The
harness (bench/phase2_*.py) is complete and needs no changes for the eventual
re-run.
Gate item 5 is CLOSED (secrets rotated 2026-07-11 — revoked in dashboards,
local copies deleted; harness branch merged and labels removed). A 2026-07-12
publish-readiness review board found three launch blockers on the v0.1.2 MCP
first-run path plus packaging majors — all fixed as v0.1.3 (tagged
2026-07-12; see CHANGELOG.md). Post-gate, WP10a sleep-time maintenance
(PR #3) and WP10b review UI (PR #4) merged 2026-07-16/17 — offline
dedupe/summarize/evict with a human review queue over MCP and the console;
default-off, first-run path pinned byte-identical; design + verification
record in docs/superpowers/specs/2026-07-16-sleep-time-maintenance-design.md.
WP1 launch execution shipped (2026-07-21): v0.2.0 (2026-07-17, feature
release) and v0.2.1 (2026-07-21, metadata-only, PR #5) are tagged and
released; MCP Registry and PyPI (lean-memory + lean-memory-console) are
LIVE at 0.2.1; v0.2.2 (2026-07-29, patch) pinned mcp>=1.2,<2 (mcp
2.0.0 removed mcp.server.fastmcp, breaking fresh installs) and shipped the
WP11 write-time restatement dedupe; v0.2.3 (2026-07-29, patch) adds dual-path mcp 1.x/2.x support (pin
>=1.2,<3, WP12), fixes the 2.0 worker-thread SQLite crash, and ships the
WP13 tool metadata (Glama re-scan) and WP2 update-integrity benchmark;
v0.2.4 (2026-08-06, patch) ships the WP14 console MCP tool metadata;
v0.3.0 (2026-08-07, minor — the current release) ships WP15 entity name
collation (entity.name_key, schema v3 in-place migration, one-way
downgrade — hence minor not patch), the lowercase-first-person extractor
fix, and the WP2 mem0 comparison arm with a published fully-local run
(issues #13–#15, #17 all closed 2026-08-06/07; only #16 signal-watch and
#18 six-week checkpoint remain open). Channel-posts decision (user,
2026-07-29): the remaining posts are OPTIONAL, not launch-required — the
Claude Code plugin marketplace form (platform.claude.com/plugins/submit) and
the Show HN / r/ClaudeAI / r/LocalLLaMA posts may go out whenever (or never);
final copy stays ready in docs/launch/launch-copy.md, runbook in
docs/launch/launch-checklist.md. awesome-mcp-servers PR #9890 MERGED
2026-07-22 (found 2026-08-06 — earlier "in review" framing was stale), so
that channel has been live since one week before window start. The six-week
demand read (spec §4) runs on the live channels (MCP Registry + PyPI +
awesome-mcp-servers), window start 2026-07-29 (v0.2.2); if further posts go
out later, note the date so the read can be segmented. Demand-read caveat
(2026-08-06): the repo's 47 stars / 44 forks are a synthetic bot burst on
2026-07-22 (Faker-style accounts, all created 2026-06-27) — exclude from the
read; organic GitHub social signal is ~3 stars.
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 · 92 lines · 1,646 tokens per session scan A c82a42219427
lean-memory CLAUDE.md is an instructions file published in the GitHub repository Wuesteon/lean-memory (47 stars, last pushed 26d ago), licensed Apache-2.0. It adds 1,646 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
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.
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).
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.