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 skills add LameGz/synapse-graph-skills --skill synapse-graph-memorygit clone --depth 1 https://github.com/LameGz/synapse-graph-skillsWrote 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/lamegz/synapse-graph-skills/synapse-graph-memory)<a href="https://agentmods.dev/skills/lamegz/synapse-graph-skills/synapse-graph-memory"><img src="https://agentmods.dev/badge/skills/lamegz/synapse-graph-skills/synapse-graph-memory/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/skills/lamegz/synapse-graph-skills/synapse-graph-memory"><img src="https://agentmods.dev/badge/skills/lamegz/synapse-graph-skills/synapse-graph-memory.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.00175 | $0.03375 |
| Opus 5 | $0.00088 | $0.01688 |
| Sonnet 5 | $0.00035 | $0.00675 |
| Haiku 4.5 | $0.00017 | $0.00337 |
Grade A, and why
synapse-graph-memory 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 9d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synapse Graph Memory
Overview
Partitioned context loading via graph topology with progressive disclosure. Each Markdown node declares cross-module dependencies in frontmatter and a one-line summary for rapid triage. Three-layer retrieval:
- Layer 1: Read MEMORY_MAP summaries — triage without commitment (~200-500 tok)
- Layer 2: Read full target node(s) — load only after confirming relevance
- Layer 3: Bounded BFS deps (depth ≤ 2, width ≤ 5) — expand only when necessary
Three CS primitives: inverted index (MEMORY_MAP for O(1) lookup), normalization (domain-split nodes), foreign-key references (depends_on edges for deterministic traversal, not vector similarity).
For the full node specification, critical rules, and common mistakes, see references/ — they are loaded on demand, not by default.
Quick Reference
| Action | Rule |
|---|---|
| Vague status / progress | Read ## Status Digest or ## Progress Summary in MEMORY_MAP.md |
| Find nodes for topic | Read MEMORY_MAP.md, match tags → aliases → keywords |
| Load memory for task | Layer 1 MAP → Layer 2 target node → Layer 3 bounded BFS (depth≤2, width≤5) |
| Compound time+domain query | Filtered BFS: decompose query → tag + date filter + section locate |
| Check downstream impact | Read blocks field in MEMORY_MAP.md before modifying any module |
| Natural-language memory write | synapse_note.sh --text "..." (one command: ingest → suggest → apply → rebuild → doctor) |
| Review queued memory | memory_inbox.py list --project <path> then memory_inbox.py apply --project <path> |
| Resume project context | project_resume.py --project <path> (MAP-first project recovery) |
| Rebuild index | Auto-run by session-end hook; manual full rebuild: generate_memory_map.sh --full; changed-node fast path: generate_memory_map.sh --changed <node>.md |
| Health check | doctor.sh — validates frontmatter, dead links, orphans, oversized nodes |
| Initialize project | init.sh — auto-detect stack, generate skeleton nodes |
What ships with it
46 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/settings.template.json 859 B
- assets/template.md 6.0 KB
- evals/evals.json 8.3 KB
- examples/solo-saas/MEMORY_MAP.json 5.1 KB
- examples/solo-saas/MEMORY_MAP.md 14 KB
- examples/solo-saas/meta/feat_admin-notification.md 846 B
- examples/solo-saas/meta/feat_login.md 949 B
- examples/solo-saas/meta/feat_subscription.md 969 B
- examples/solo-saas/meta/mod_auth-api.md 918 B
- examples/solo-saas/meta/mod_payment.md 887 B
- examples/solo-saas/meta/mod_user-account.md 905 B
- examples/solo-saas/package.json 130 B
- examples/solo-saas/prisma/schema.prisma 187 B
- examples/solo-saas/src/auth/routes.ts 105 B runs code
- examples/solo-saas/src/pages/login.tsx 88 B
- examples/solo-saas/src/payment/routes.ts 77 B runs code
- references/common-mistakes.md 2.1 KB
- references/critical-rules.md 6.3 KB
- references/fullstack-node-spec.md 4.6 KB
- references/node-spec.md 4.8 KB
- scripts/apply_memory_proposal.py 8.8 KB runs code
- scripts/auto_observe.py 13 KB runs code
- scripts/benchmark.sh 20 KB runs code
- scripts/db_index.py 5.9 KB runs code
- scripts/db_init.py 3.5 KB runs code
- scripts/demo_solo_saas.sh 1.9 KB runs code
- scripts/doctor.sh 6.2 KB runs code
- scripts/generate_memory_map.py 19 KB runs code
- scripts/generate_memory_map.sh 47 KB runs code
- scripts/hooks/post-tool-use.sh 4.3 KB runs code
- scripts/hooks/pre-modify-check.sh 6.0 KB runs code
- scripts/hooks/pre-read-check.sh 2.9 KB runs code
- scripts/hooks/session-end.sh 21 KB runs code
- scripts/ingest_memory.py 7.0 KB runs code
- scripts/init.sh 23 KB runs code
- scripts/memory_inbox.py 7.9 KB runs code
- scripts/parse-session.sh 14 KB runs code
- scripts/project_resume.py 4.6 KB runs code
- scripts/query_timeline.sh 8.1 KB runs code
- scripts/release_check.sh 2.3 KB runs code
- scripts/source_scan.py 10.0 KB runs code
- scripts/suggest_edges.py 5.9 KB runs code
- scripts/suggest_edges.sh 18 KB runs code
- scripts/synapse_note.sh 4.8 KB runs code
- scripts/visualize.py 1.6 KB runs code
- scripts/watch.sh 3.7 KB runs code
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.
- 9d ago First seen · 276 lines · 175 tokens per session scan A 44f3c22ae2d3
synapse-graph-memory is a skill published in the GitHub repository LameGz/synapse-graph-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 175 tokens to every session and 3,375 once invoked, about $0.0009 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 skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.