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 rules/putervision/webcrypt/state-graph-mcpgit clone --depth 1 https://github.com/putervision/WebCryptWhat 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.00562 | $0.00562 |
| Opus 5 | $0.00281 | $0.00281 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
state-graph-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 yesterday.
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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Graph (state-graph-mcp)
This project tracks workflow state, tasks, design decisions, and blockers using state-graph-mcp.
1. Priority Order
Before doing any coding or investigation:
get_project_summary— Always run this first to understand current project state, active branches, and overall progress.find_blockers— Identify any active blockers preventing progress.list_nodes— Find pending tasks, past decisions, or milestones.trace_dependencies— 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 new task: Create a node with
add_node(type: "task", title: "..."). - Making a design or implementation decision: Document it with
add_node(type: "decision", title: "...", metadata: { "rationale": "..." }). - Encountering a blocker: Record the blocker with
add_node(type: "blocker", ...)and connect it to the blocked task usingadd_edge(type: "blocks", source_id: blocker_id, target_id: task_id). - Completing a task: Update the status to done using
update_node(id: task_id, status: "done"). - Creating/generating a new file: Create an artifact node with
add_node(type: "artifact", ...)and connect it usingadd_edge(type: "produces").
3. Workflow Pattern
- Start of session: Run
get_project_summaryandfind_blockersto align on current status. - Task decomposition: Decompose user requests into tasks and add them to the graph.
- Execution: Mark tasks as "in_progress", document design decisions as they occur, and log blockers if you hit any obstacles.
- Resolution: Mark tasks as "done", document completed artifacts, and resolve blockers.
4. Codebase Seeding on Initialization
If the project was just initialized or is missing high-level structure (Plans, Milestones, Decisions):
- Inspect the Codebase: Read the README and core files to understand the roadmap and architecture.
- Scaffold the Roadmap: Create a
plannode (e.g., "Project Roadmap") and addmilestonenodes representing key target phases, connecting them usingpart_ofedges. - Scaffold Architecture: Create
decisionnodes representing core technical choices (e.g., choice of databases, frameworks) and link them to the milestones/tasks usingdecided_inedges.
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.
- yesterday First seen · 31 lines · 562 tokens per session scan A 74394a76b86d
state-graph-mcp is a cursor rule published in the GitHub repository putervision/WebCrypt (26 stars, last pushed 10d ago), licensed MIT. It adds 562 tokens to every session, about $0.0028 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.