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/putervision/state-memory-mcp/claude-mdgit clone --depth 1 https://github.com/putervision/state-memory-mcpWrote 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/putervision/state-memory-mcp/claude-md)<a href="https://agentmods.dev/instructions/putervision/state-memory-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/putervision/state-memory-mcp/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.01821 | $0.01821 |
| Opus 5 | $0.00911 | $0.00911 |
| Sonnet 5 | $0.00364 | $0.00364 |
| Haiku 4.5 | $0.00182 | $0.00182 |
Grade B, and why
state-memory-mcp CLAUDE.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 4d 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.
* **Google Antigravity (`~/.gemini/config/config.json`)**: Add these rules to your `"globalPermissionGrants"` -> `"allow"` list: This is a copy
100% identical to state-memory-mcp copilot-instructions.md — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Memory (state-memory-mcp)
This project tracks workflow state, tasks, design decisions, and blockers using state-memory-mcp with project slug "state-memory-mcp".
1. Priority Order
Before doing any coding or investigation:
manage_sessions(action: "start")— Start a tracking session for full change attribution.get_analytics(action: "summary")— Run to understand current project state, active branches, and overall progress.manage_tasks(action: "next")— Query prioritized runnable tasks.manage_tasks(action: "find_blockers")— Identify any active blockers preventing progress.manage_nodes(action: "list")— Find pending tasks, past decisions, or milestones.query_graph(action: "trace")— Trace what depends on or blocks a task.
2. When to Write to the Graph
You MUST update the graph as you work:
- Starting a session: Always call
manage_sessions(action: "start", agent_id: "my-agent")to track all mutations under a unique session. - Starting a new task: Create a node with
manage_nodes(action: "create", type: "task", title: "...", session_id: session_id). - Making a design or implementation decision: Document it with
manage_nodes(action: "create", type: "decision", title: "...", metadata: { "rationale": "..." }, session_id: session_id). - Connecting UI tasks to visual states: Use
manage_edges(action: "link_visual", target_id: task_id, visual_state_id: vs_id, relationship: "renders_state"). - Encountering a blocker: Record the blocker with
manage_nodes(action: "create", type: "blocker", ..., session_id: session_id)and connect it usingmanage_edges(action: "add", type: "blocks", source_id: blocker_id, target_id: task_id, session_id: session_id). - Adding observation notes: Atomically log notes using
manage_nodes(action: "add_note", text: "...", attach_to: node_id). - Batch updates: Bulk update tasks/nodes using
manage_nodes(action: "batch_update", ids: ["..."], status: "done"). - Observability & Trajectories: Check
manage_data(action: "export_synergy_metrics")for combined token savings & health, andmanage_data(action: "export_joint_trajectories")for interleaved fine-tuning datasets. - Completing a task: Update status to done using
manage_tasks(action: "complete", task_id: task_id). - Creating/generating a new file: Create an artifact node with
manage_nodes(action: "create", type: "artifact", ..., session_id: session_id)and connect it usingmanage_edges(action: "add", type: "produces", ..., session_id: session_id).
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.
- 4d ago First seen · 82 lines · 1,821 tokens per session scan B 83ee082c70a6
state-memory-mcp CLAUDE.md is an instructions file published in the GitHub repository putervision/state-memory-mcp (79 stars, last pushed 15d ago), licensed MIT. It adds 1,821 tokens to every session, about $0.0091 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 100% identical to state-memory-mcp copilot-instructions.md, differing in 1 line, and is treated as a copy.
Other instructions, from other repositories
rekal CLAUDE.md
Instructions for janbjorge/rekal, a project described as: Long-term memory for LLMs. MCP server backed by hybrid search in a single SQLite file.
swag-mcp CLAUDE.md
Claude Code instructions for jmagar/swag-mcp, covering swag mcp - claude memory reference, project overview, core architecture, key components and common development commands.
toon-memory AGENTS.md
Instructions for LuiggiVal08/toon-memory, covering agents.md, build & verify, architecture, smarter memory pattern and visual memory pattern.
immichctrl AGENTS.md
Instructions for lidless-labs/immichctrl, covering agents.md - working in this repo, every session, definition of done, memory owner and memory handoff (mandatory).
immichctrl CLAUDE.md
Instructions for lidless-labs/immichctrl, covering claude.md - claude code rules, project rules, memory handoff, brigade work loop (mandatory) and closeout.
munin-memory AGENTS.md
AGENTS.md instructions for Magnus-Gille/munin-memory, covering munin memory — project instructions, instruction contract, project purpose and architecture, sources of truth and session and state discipline.