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.
git clone --depth 1 https://github.com/putervision/WebCryptWrote 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/rules/putervision/webcrypt/state-memory-mcp)<a href="https://agentmods.dev/rules/putervision/webcrypt/state-memory-mcp"><img src="https://agentmods.dev/badge/rules/putervision/webcrypt/state-memory-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/putervision/webcrypt/state-memory-mcp"><img src="https://agentmods.dev/badge/rules/putervision/webcrypt/state-memory-mcp.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00881 | $0.00881 |
| Opus 5.5 | $0.00352 | $0.00352 |
| Sonnet 5.5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
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 1mo 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.
This is a copy
95% identical to state-memory-mcp — 2 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.
How it starts
The opening of the file, as written. The whole thing — 36 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 "webcrypt".
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). - Encountering a blocker: Record the blocker with
manage_nodes(action: "create", type: "blocker", title: "...", 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"). - Completing a task: Update status to done using
manage_tasks(action: "complete", task_id: task_id)ormanage_nodes(action: "update", id: task_id, status: "done"). - Creating/generating a new file: Create an artifact node with
manage_nodes(action: "create", type: "artifact", title: "...", session_id: session_id)and connect it usingmanage_edges(action: "add", type: "produces", source_id: task_id, target_id: artifact_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.
- 1mo ago First seen · 36 lines · 881 tokens per session scan A fda59aafc259
state-memory-mcp is a cursor rule published in the GitHub repository putervision/WebCrypt (14 stars, last pushed 1mo ago), licensed MIT. It adds 881 tokens to every session, about $0.0035 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to state-memory-mcp, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
project-memory
This rule guides recording project events and decisions in projectmem.
decision-logger
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting…
team-brain
Team Brain sync mode — one start per ticket, then live merge-safe crew memory. Always-on when .team-brain exists or work mentions an initiative/Jira key.
swamr-obsidian-brain
Swamr Obsidian Brain — persistent knowledge base that agents read from and write to across phases. Prevents context loss by maintaining architecture decisions, task outputs, learned patterns, and project knowledge in an Obsidian vault. Every agent MUST read relevant notes before starting and write a summary note when…
jarvis-agent-rules
MCP server jarvis: notes, Jira, knowledge graph, sessions, preferences.
project-with-reflect
Use project-with-reflect persistent project memory and reflection workflow.