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-graph-mcp)<a href="https://agentmods.dev/rules/putervision/webcrypt/state-graph-mcp"><img src="https://agentmods.dev/badge/rules/putervision/webcrypt/state-graph-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-graph-mcp"><img src="https://agentmods.dev/badge/rules/putervision/webcrypt/state-graph-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.00562 | $0.00562 |
| Opus 5.5 | $0.00225 | $0.00225 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 (14 stars, last pushed 1mo ago), licensed MIT. It adds 562 tokens to every session, about $0.0022 per session on Opus 5.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
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.
workflow-examples
CRITICAL: Contains mandatory examples for correct workflow implementation. DO NOT assume workflow patterns without consulting this documentation first.