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/shofer-dev/claude-code-live-memory/agents-mdgit clone --depth 1 https://github.com/shofer-dev/claude-code-live-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.01254 | $0.01254 |
| Opus 5 | $0.00627 | $0.00627 |
| Sonnet 5 | $0.00251 | $0.00251 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
claude-code-live-memory 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working agreements — Live Memory
Rules for anyone (human or agent) changing this repo. Keep it short and
high-signal — durable rules only, current-state. Full design: DESIGN.md.
What this is
A Claude Code plugin: a persistent, read-only, large-context codebase-Q&A
companion. One long-running HTTP MCP server (Python/asyncio) exposes a single
tool, ask_live_memory, and accumulates repo knowledge across sessions. State
is keyed per workspace (cwd). See DESIGN.md for the full rationale.
Stack & conventions
- Python ≥ 3.10, asyncio. Server code lives in
server/live_memory/; it's a standalone package (server/pyproject.toml). Key deps:mcp(FastMCP, streamable-http),anthropic,starlette,uvicorn,watchdog. - Type checking is
mypy --strict(pyproject.toml, excludestests/). No ruff/black/flake8 is configured — don't assume a formatter runs. - All tunable magic numbers live in
server/live_memory/constants.py— no scattered literals. - Add a runtime dep = edit
pyproject.tomldependencies+pip install -e .. New source files are auto-discovered (setuptools) — no manual srcs list.
Test / gate
./run-tests.sh(repo root) is the gate:mypy live_memory/thenpytest -q, bootstrappingserver/.venvwith.[dev]if needed. It's the pre-push hook (git-hooks/pre-push; install once viagit-hooks/install.sh). Leave the tree green before committing.- Faster inner loop from
server/:mypy live_memory/+pytest -m "not integration" -q. Tests are fully mocked (fake LLM, mocked httpx/OAuth) — no network or API key needed.
Running / deploying the server
- The server must already be running before Claude Code connects.
.mcp.jsonistype: http— Claude Code connects, never spawns it; if it's down you get a connection error. Dev:cd server && pip install -e . && python -m live_memory→http://127.0.0.1:7711/mcp(+/health,/stats,/notify,/reload). - Prod = a user systemd service on :7711 via
deploy/install-service.sh(defaults to a user service — required so zero-config subscription OAuth can read~/.claude/.credentials.json). It's a supervised singleton serving every session: restart withsystemctl --user restart live-memory; never kill it ad hoc — that breaks every connected session (and systemd restarts it anyway). - Model/provider: set via env (
LIVE_MEMORY_*) or the/live-memory-configcommand, which writesconfig.jsonin the data dir and hot-reloads viaPOST /reload— no restart. Precedence: env > config.json > defaults.
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 · 84 lines · 1,254 tokens per session scan A cb12bb076be7
claude-code-live-memory AGENTS.md is an instructions file published in the GitHub repository shofer-dev/claude-code-live-memory (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,254 tokens to every session, about $0.0063 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
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.