state-memory-mcp

A persistent graph-based memory service for tracking project sessions, tasks, decisions, blockers, plans, milestones, artifacts, and their relationships. A graph database stores connected pieces of information so dependencies can be followed.

In plain words
What is it for?
Use it before coding or investigation to start a session, review project status and requirements, find the next task and blockers, and trace dependencies between work items.
Why use it?
It keeps workflow context across sessions and shows what is unfinished, blocked, or dependent on another item.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/putervision/webcrypt/state-memory-mcp
Any agent
npx skills add putervision/WebCrypt --skill state-memory-mcp
Clone the repo
git clone --depth 1 https://github.com/putervision/WebCrypt

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,940 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.01940
Opus 5 $0.00023 $0.00970
Sonnet 5 $0.00009 $0.00388
Haiku 4.5 $0.00005 $0.00194

Measured 2d ago against content hash e1f0f3d27fd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

state-memory-mcp 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.

Origin

This is a copy

95% identical to state-memory-mcp — 40 lines 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.

.agents/skills/state-memory-mcp/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

State Memory (state-memory-mcp) — 13 Consolidated Tools

This project uses state-memory-mcp with project slug "webcrypt" to provide AI agents with a structured, persistent graph for tracking workflow state.

1. Priority Order & Mandatory Checklist

Before doing any coding or investigation, you MUST run this sequence:

  1. manage_sessions(action: "start") — Start a tracking session with an agent_id for full change attribution.
  2. get_analytics(action: "summary") — Understand current project state, active branches, and overall progress.
  3. manage_specs(action: "compliance") — Check real-time requirement coverage matrix and unfulfilled criteria.
  4. manage_tasks(action: "next") — Query prioritized runnable tasks (sorted by downstream impact and age).
  5. manage_tasks(action: "find_blockers") — Identify any active blockers preventing progress.
  6. manage_nodes(action: "list") — Find pending tasks, past decisions, or milestones.
  7. query_graph(action: "trace") — Trace what depends on or blocks a task.

2. Complete 13 Consolidated MCP Tools Reference

# Tool Name Key Actions Description
1 manage_nodes create, update, get, remove, list, search, batch_create, batch_update, add_note Graph node CRUD, full-text / TF-IDF search, atomic batch operations, and quick notes.
2 manage_edges add, remove, batch_add, link_visual Manage typed graph relationships and link tasks/artifacts to visual memory state IDs.
3 manage_sessions start, end, list, bootstrap Agent tracking sessions, attribution, and single-turn context bootstrapping.
4 manage_tasks next, complete, find_blocked, find_stale, find_blockers, find_similar_blockers, auto_prune Prioritized task queue, task completion, blocker detection, and automated stale pruning.
5 manage_snapshots save, list, diff, get_state, revert, undo, get_history Graph checkpoints, visual diffs, point-in-time state reconstruction, and rollbacks.
6 manage_specs scaffold, ingest, export, compliance, verify, decompose_feature, template Spec-Driven Development (SDD), PRD parsing, acceptance verification, and FDD/RFC templates.
7 manage_database backup, restore, audit, merge, branch_diff, branch_merge SQLite maintenance, physical backups, integrity audits, and Git branch state diffs/merges.
8 manage_data export_graph, export_issues, export_trajectories, export_joint_trajectories, export_synergy_metrics, import_graph, import_issues, import_spec Bulk import/export of graph formats, GitHub/Jira issues, ML trajectories, and ROI synergy metrics.
9 query_graph subgraph, trace, raw, natural_language Graph traversal, upstream/downstream dependency tracing, raw SQL queries, and natural language search.
10 get_analytics summary, velocity, burndown, value_metrics, cognitive_load, critical_path, context_snapshot, decision_trail, find_related_decisions, contradictions Analytics suite: project overview, velocity, burndown, token ROI, cognitive load, and decision trails.
11 get_events log, changelog, post_mortem Append-only event log queries, session changelogs, and automated session post-mortems.
12 run_diagnostics validate, doctor, check_refs, audit_chain, compact, archive, prune_events, version Graph integrity validation, doctor health checks, SHA-256 hash audits, compaction, and archiving.
13 use_blackboard post, read Asynchronous multi-agent notice board for inter-agent coordination with TTL expiration.

Read the full file on GitHub · 106 lines

Changes

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.

  1. 2d ago First seen · 106 lines · 45 tokens per session scan A e1f0f3d27fd1

Subscribe to this mod's changes

state-memory-mcp is a skill published in the GitHub repository putervision/WebCrypt (24 stars, last pushed 11d ago), licensed MIT. It adds 45 tokens to every session and 1,940 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to state-memory-mcp, differing in 40 lines, and is treated as a copy.

Related

Other skills, from other repositories

Cryptographic Analysis & Assessment

SSL/TLS auditing, cipher suite analysis, hash algorithm identification, encryption implementation review, and cryptographic weakness detection in code.

Masriyan/Claude-Code-CyberSecurity-Skill · 30 tokens

analyzing-ransomware-encryption-behavior

Analyzes how a ransomware sample encrypts files: identifying the crypto scheme (symmetric/asymmetric/hybrid), key handling, file targeting and extension/marker changes, shadow-copy deletion, and ransom-note artifacts. Activates for requests to analyze ransomware encryption, assess decryptability, or study ransomware…

meltedinhex/analyst-ai-pack · 72 tokens

covalent-bond-test

How to write, run, and debug tests for Covalent Bond: the runner, the in-process mock relay, deterministic polling, port allocation, cleanup conventions, and what every kind of change must cover. Use when adding or modifying a test, when a suite fails, or before committing any behavior change.

gopalrajsuresh/covalent-bond · 68 tokens

covalent-bond-run

How to run Covalent Bond on a machine and pair two AI agents, covering how to register the MCP server, start a relay (mock or deployed), create/join a session, send files, and troubleshoot. Use when a user wants to set up, start, connect, or test Covalent Bond, or asks why a session won't connect.

gopalrajsuresh/covalent-bond · 77 tokens

covalent-bond-self-relay

Deploy the user's own Covalent Bond relay to their Cloudflare account: install wrangler, walk them through the browser login, run the deploy, verify /health, and set COVALENTRELAYURL. Use when a user asks to set up, deploy, or host their own relay instead of using the public one.

gopalrajsuresh/covalent-bond · 75 tokens

covalent-bond-guardrails

Guardrails for any agent editing the Covalent Bond repository, covering the security invariants that must never be broken, what code NOT to add, and the verify-don't-guess working discipline. Use whenever writing or changing code, tests, or config in this repo before making the edit.

gopalrajsuresh/covalent-bond · 68 tokens