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 skills/putervision/spc/state-memory-mcpnpx skills add putervision/spc --skill state-memory-mcpgit clone --depth 1 https://github.com/putervision/spcWrote 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/skills/putervision/spc/state-memory-mcp)<a href="https://agentmods.dev/skills/putervision/spc/state-memory-mcp"><img src="https://agentmods.dev/badge/skills/putervision/spc/state-memory-mcp.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.00045 | $0.01875 |
| Opus 5 | $0.00023 | $0.00937 |
| Sonnet 5 | $0.00009 | $0.00375 |
| Haiku 4.5 | $0.00005 | $0.00187 |
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 3d 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
98% 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 — 98 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 "spc" 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:
manage_sessions(action: "start")— Start a tracking session with anagent_idfor full change attribution.get_analytics(action: "summary")— Understand current project state, active branches, and overall progress.manage_specs(action: "compliance")— Check real-time requirement coverage matrix and unfulfilled criteria.manage_tasks(action: "next")— Query prioritized runnable tasks (sorted by downstream impact and age).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. 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. |
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.
- 3d ago First seen · 98 lines · 45 tokens per session scan A 6bd8a5a5657e
state-memory-mcp is a skill published in the GitHub repository putervision/spc (39 stars, last pushed 13d ago), licensed MIT. It adds 45 tokens to every session and 1,875 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to state-memory-mcp, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
analyzing-packed-malware-with-upx-unpacker
Identifies and unpacks UPX-packed malware samples, including binaries with modified UPX magic bytes or headers that block automated decompression, to recover the original executable for static analysis. Use when a sample shows high entropy, minimal imports, or only LoadLibrary/GetProcAddress in its import table, or…
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects. Use when triaging a suspicious PDF attachment from a phishing email, analyzing a PDF-based exploit document, or building detection signatures for weaponized PDF…
analyzing-android-malware-with-apktool
Perform static analysis of Android APK malware using apktool for resource decompilation, jadx for Java source recovery, and androguard for manifest inspection, dangerous permission-combination detection, and identification of obfuscated code, dynamic code loading, and reflection-based API calls. Use to statically…
cli-analysis
Run the pyscn command-line tool for Python code quality analysis - CI/CD quality gates, HTML/JSON/CSV reports, full analysis runs, and project configuration. Use when user wants a CI check, a shareable report file, or to configure pyscn for a project.
health-check
Get an overall Python code quality health score using pyscn. Use when user asks how healthy or good the code is, wants a quality overview, a grade, a summary of technical debt, or a before/after quality comparison.
architecture-review
Analyze Python module architecture using pyscn - class coupling (CBO), cohesion (LCOM), dependency cycles, and module communities. Use when user asks about architecture, module structure, coupling, circular dependencies, or which files to review or change together.